BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage SOA Content on InfoQ

  • "Code First" Web Services Reconsidered

    In this article, Dennis Sosnoski questions the conventional wisdom that a contract-first approach to web services development, i.e. starting from WSDL, is superior to starting from code. He shows how the JiBX framework can be used to practice start-from-code development without incurring the disadvantages, specifically without coupling implementation and interface too tightly.

  • Service Composition

    In this article, Boris Lublinsky discusses the main approaches to service composition, both from design and implementation point of view, and outlines the benefits of using orchestration. Topics covered include hierarchical vs. conversational composition, composition topologies, and the pros and cons of difference implementation approaches.

  • Roles in SOA Governance

    To make sure SOA succeeds, many vendors, analysts, consultants and practitioners agree that Governance is a critical ingredient for a successful SOA initiative. This article explores a potential set of roles for successful SOA Governance, the roles of "SOA Domain Architect", "SOA Platform Architect", "Service Designer", "Business Service Owner", and "Technical Service Owner".

  • Eric Newcomer on the future of OSGi

    Eric Newcomer, co-chair of the OSGi Enterprise work group, talks about the evolution of OSGi and it's relationship to SOA and ESB. He discusses how he thinks OSGi will evolve over the coming years and whether or not it makes sense for Sun to adopt OSGi as the container model of choice."

  • Bridging the gap between BI & SOA

    Business intelligence (BI) and service-oriented architecture (SOA) have conflicting principles and needs. SOA promotes hiding the data inside the services while BI needs that very data if we want to get meaningful predictions and alerts. This article will show you how you can combine SOA with EDA to solve the BI/SOA conflict and maybe even enhance your SOA.

  • Service Firewall Pattern

    How can you protect a service against detect malicious incoming messages and prevent information disclosure on outgoing messages? In this sample chapter from Arnon Rotem-Gal-Oz' in-progress book SOA Patterns, Arnon explains how to use a Service Firewall to intercept incoming and outgoing messages and inspect them in a dedicated software component or hardware.

  • Service Oriented Architecture Governance: The Basics

    In this article, MomentumSI's Ed Vazquez explains the basics of SOA governance, with an explicit focus on the need for a holistic SOA governance model, shared governance principles and the difference between (and the need for both) tactical and strategic efforts.

  • Unit-Testing XML

    There are many occasions where software creates XML output: XML documents are used for data interchange between different applications, web application create (X)HTML output or respond to AJAX requests with XML, and this has to be tested as much as anything else. In this article, Stefan Bodewig explains how to perform those tests with the XMLUnit framework he has co-authored.

  • Interview and Book Excerpt: RESTful Web Services

    Today, InfoQ publishes a sample chapter from RESTful Web Services, a book authored by Leonard Richardson and Sam Ruby. The book covers the principles of the REST style, and explains how to build RESTful applications using Java, Ruby, and Python. InfoQ's Stefan Tilkov had a chance to talk to the authors about their motivations for writing this book and their views on REST and Web services.

  • Implementing Exceptions in SOA

    In this InfoQ article, Boris Lublinsky highlights the problems with exception handling in SOA, and suggests a SOA-based solution: a logging service that accepts all logging requests, stores and forwards them to an exception resolution service, which is responsible for enforcing rules about exception resolution, a notification service, an exceptions/logging portal, and service management.

  • Case Study: Composite Applications at Safeco

    A case study about how motor vehicle insurance records company Safeco used SOA approahes, SCA, BPEL, and composite application approaches to reuse legacy code, enable runtime modifiability thanks to decoupling, Java and .NET interoperability, and the ability to deliver a complex solution integrating over 5 systems in less than 8 weeks with a small team.

  • Case study: A new approach to integrating architectures post-merger at Lawson

    The merger of Lawson and Intentia in 2006 left developers with an important problem to solve - the integration and presentation of legacy applications and business services that are constructed in Java, .NET, and other technologies. This case study looks under the hood at the new architecture at Lawson and how they got there.

BT