Many teams are actively refreshing their integration platform and evaluating open source ESB (Enterprise Service Bus) capabilities and benefits.Â Fewer are evaluating their SOA strategy and establishing open source SOA (Service Oriented Architecture) platform infrastructure, metrics, and measurements required to guide teams towards agility and responsiveness.
Back in 2009, Dion Hinchcliffe described how SOA infrastructure “can indeed really help make the transition to SOA faster and easier”. He also described how the situation “is increasingly becoming a head-to-head competition between commercial and open source SOA solutions.” Â Four years later, proprietary SOA products are further marginalized by open source SOA affordability, performance, and comprehensive capabilities.
When comparing ESB products, you will notice almost all Enterprise Service Bus products support enterprise integration patterns, deliver all required ESB features (i.e. web services, message transformation, protocol mediation, content routing), and offer a graphical development workbench. ESB Proof of Concept (PoC) evaluations are often won or lost based on the productâ€™s extensibility and roadmap and vendorâ€™s responsiveness and open source culture.Â Â Dion mentions the open source SOA value in â€œThe transparency of and ability to influence open source projects continues to be no small factor either as implementers struggle with more opaque less-frequently updated commercial products.â€Â In complementary technology spheres (e.g. Cloud, API Management) with increasing velocity, the transparency and influence value proposition is a business imperative.
While integration teams may use an open source ESB to rapidly integrate service endpoints, a broader value proposition is gained when integration teams use an open source ESB to eliminate service-oriented anti-patterns of isolation, uniqueness, and duplication.Â To reduce service-oriented anti-patterns, teams desire to share and re-use assets, consolidate functionality, and conform projects to common standards.Â Â To achieve these best practices, teams rely on an open source ESB to deliver the following required architectural attributes:
â–ªÂ Â Interoperability
â–ªÂ Â Abstraction
â–ªÂ Â Resource location virtualization
â–ªÂ Â Ability to scale and manage service
â–ªÂ Â Declarative policies and platform independent models
â–ªÂ Â Separation of concern
â–ªÂ Â Loose coupling
At a minimum the open source ESB implementation should encourage mediation flow re-use that decrease unique service endpoint definitions by bridging disparate protocols, message formats, and locations.
Strive to avoid complexity and inefficiency by specifying an optimal platform component mix, defining â€˜the right tool for the jobâ€™, and developing scalable, agile integration solutions.Â Â In a ‘selecting an open source ESB webinar, I propose an integration reference architecture decision framework, ESB use cases, and product selection guidelines.
When teams expect SOA benefits, but only rely on an open source ESB, many development teams publish services, yet struggle to create a service architecture that is widely shared, re-used, and adopted across internal development teams.
On your road to SOA, you will find an open source ESB is the first cornerstone of an open source SOA, and the other three SOA platform corners are filled with governance registry, message broker, and data service servers encourage SOA patterns and practices.
An open source SOA & Integration Platform guides integration teams towards implementing best-practice SOA patterns, overcoming SOA anti-patterns, and implementing SOA principles across message bus, registry, service monitoring, legacy applications, message queues, business service, and data service components.Â Â For example, a governance registry promotes sharing schema models and meta-data to reduce duplicative implementations. Â A list of platform components to consider incudes:
Open source ESB (Enterprise Service Bus): delivers content routing, protocol mediation, and message transformation that loosely couples service consumer from service provider.Â An ESB adapts protocols, formats, and interaction styles to connect with any IT asset by implementing Enterprise Integration Patterns and Message Exchange Patterns
Open Source Governance Registry: store development-time and run-time policies, track dependencies, facilitate lifecycle management, encourage team collaboration, and guide the development process.
Open Source Message Broker: exchanges communications asynchronously or publishes messages for timely access by many subscribers.
Open Source Business Process Server:Â standardize and automate human workflow, orchestrate long-running and stateful business process activity, and integrate applications with business process services.
Open Source Data Services Server: provides a lightweight, developer friendly, agile development approach for secure and managed integration across federated data stores, performing data transformation, enforcing data validation, creating composite data views, and exposing data as a services.
Open Source Business Rules Server:Â brings the agility of shared business rules to your SOA Platform.Â A single rule set across all service operations allows working memory state sharing across business rule invocations
Open Source Application Server: exposes multi-tenant service endpoints sharing business logic, data, and process across the entire IT ecosystem.
Achieving SOA governance and a SOA portfolio require focused strategies, consistent programs, and collaborative execution. Ad hoc SOA governance programs often fall far short of encouraging consumer adoption, tracking service consumption, and illustrating business value. Too often, there is little or no insight into service reuse and:
- How to enable business functionality as an API or service
- Who is writing re-usable APIs or services
- Who is consuming APIs and services
- How APIs and services are being used
You may have invested significant time and effort creating services.Â Have you reached maximum service agility, adaptability, adoption? Are applications now easier to build? Is it time for a SOA portfolio review?
SOA portfolio review objectives include determining if the service-design methodology, service contract boundaries, and service coupling minimize portfolio redundancy and duplication while maximizing adoption. Â To achieve SOA benefits, many forward thinking teams complement SOA governance strategies with API management to drive service reuse and maximize open source SOA success.
To achieve SOA success and reduce SOA anti-patterns, build a strategy, adoption plan, and infrastructure. Â When considering open source ESB and an open source SOA over a closed source, proprietary ESB and SOA, Â Ron Schmelzer’s advice to
“consider OSS and vendor solutions equally and evaluate them on an equal footing. You might be surprised to find what truly fits the bill for your SOA implementation needs.Â Check your FUD at the door. Make sure you arenâ€™t losing an advantage by prematurely eliminating OSS from your SOA infrastructure mix.”
Ron made his recommendation three years ago, and the open source SOA value proposition is even stronger today. The open source SOA landscape has advanced and evolved since Jeff Davis wrote hisÂ open source SOA book. Â Maybe it is time for us all to update our open source ESB and open source SOA story.