Document Controls
For Enterprise Architecture Professionals
| Primary Analyst Photo | Document Information | Rate this Document |
|---|---|---|
|
September 12, 2007 Learn How To Embrace Lightweight ESBsLightweight ESBs Should Be An Option Within Your SOA Strategyby Mike Gilpin, Larry Fulton with Carey Schwaber, Kahini Ranade |
Average: 6
(6 ratings)
|
This is an excerpt
Executive Summary
Enterprise service buses (ESBs) come in a wide range of shapes and sizes, and some are so loaded with capabilities that they can take months to fully implement. Such complexity is one reason why developers often seek the simple solution: a lightweight ESB. Yet this choice may result in long-term problems for enterprise architects who are trying to optimize infrastructure across multiple projects. To resolve this tension, architects should embrace simplicity and guide developers toward lightweight solutions that can also fit into a broader enterprise service-oriented architecture (SOA) strategy, rather than fighting simplicity and being seen as agents of complexity.
TABLE OF CONTENTS
- A Lightweight ESB Can Be A Bone Of Contention For Developers And Architects
- Architects Should Incorporate Lightweight ESBs Into Their SOA Strategies
WHAT IT MEANS
- EA: ESBs Will Evolve To Play Specialized Roles In Your SOA Infrastructure
- Vendors: The Demand For Lightness Makes Interoperability Essential
RECOMMENDATIONS
- EA: Guide Developers To A Lightweight ESB That Fits Long-Term Strategy
- Supplemental Material
- Related Research Documents
This is an excerpt
Buy Risk-Free
Price: US $499
Our Service Guarantee: If you are not completely satisfied with this document, notify Forrester within 24 hours of purchase for a full refund.
Already a Forrester Client?
Log in to read this document.
