|By Dave Chappell||
|February 25, 2004 12:00 AM EST||
Applications are increasingly being developed "built-to-integrate," providing the ability to easily expose key functionality through commonly defined interfaces. Gartner calls this concept SODA, or Service-Oriented Development of Applications, fitting into its overall Service-Oriented Architecture landscape. When applied to the ever-present integration challenge, SODA represents a transition to service-oriented integration.
In this presentation, Chappell will examine the leading choices for supporting service-oriented integration: enterprise service buses (ESBs), integration brokers, and application suite platforms.
We will learn how making the right architectural decisions is absolutely vital to ensuring success with service-oriented integration projects - whether applications were built to integrate or not. Choices at all levels - from application interface style to overall system architecture - can seriously affect the long-term value derived from integration projects.The session will review application integration approaches being used today, and discuss how they dramatically affect architectural directions that should be carefully examined before embarking on an integration strategy.
Web Services Journal
"The New Integration Architect:You" (The importance of tools for creating and managing XSLT transforms)
"Reliable SOAP for Web Services Messaging Has Finally Arrived!" (on WS-Reliability)
"Asynchronous Web Services"
- ESB Myth Busters: 10 Enterprise Service Bus Myths Debunked
- ESB Integration Patterns
- Universal Middleware: What's Happening With OSGi and Why You Should Care
- Guaranteed Messaging With JMS
- Benchmarking JMS-Based E-Business Messaging Providers
- Distributed Logging Using The JMS
- Reconstructing J2EE-Java Business Integration Meets the Enterprise Service Bus
- Service-Oriented Integration: Making the Right Choices to Support Next-Generation Integration
- The Java Message Service
- A Real-World Example