Location: Architecture trackTime: 2007-11-13 14.00Level: Intermediate
|
|
Johan Eltes, Callista ,SwedenJohan has been consulting in the areas of object computing, distributed objects, integration platforms, Java EE and service- oriented architectures since the inceptions of these concepts and technologies. In his most recent projects, he has pioneered service- oriented solutions built on the principles of Service Component Architecture. He is currently busy establishing reference architectures for regional and national healthcare IT initiatives. He's known for combining architectural vision with practical hand-on guidance.
|
|
From ESB spaghetti to Service Oriented IntegrationThere is often a large semantic gap between the requested integration solution as expressed by business and the architecture of the solution deployed on an enterprise service bus. Integration teams sometimes experience that the application spaghetti resolved by deploying an ESB, hits back as spaghetti on the bus itself. Could service-oriented integration come to the rescue? And how does it fit into an ESB based on messaging technologies? This speech presents an approach for resolving ESB spaghetti by applying the principles of Service Component Architecture when designing and implementing integration solutions (now service components and composite applications!) to an Enterprise Service Bus (examples from WebSphere Message Broker / ESB Advanced). The presentation covers the following topics: * Problem definition - business case for service-oriented integration * How service-oriented integration patterns differ from event- driven counter-parties * Challenges of routing asynchronous service invocations * Reengineering a flow-based ESB solution into collaborating , composite services - based on a reference model for Service-Oriented Integration * How re-use- and versioning comes "for free" * What we don't get (or why we still, but to less extent, may need BPEL) * The need for supporting metadata * Summary of experience gained from a pilot
|
