Category Archives: Enterprise Service Bus

Re-shaping Your Enterprise Integration Architecture

To accelerate agility and increase time to market, a Connected Business relies on accessible and integrated business capabilities.  A leading edge integration platform can reshape your enterprise integration architecture and create an integration environment where project teams can easily and rapidly connect, re-use, and compose data, APIs, and services into effective business solutions.

Key challenges

Your business customers and partners expect rapid, low-cost access to timely information, and each business project requires integrating numerous back-end legacy systems, SaaS applications, and data feeds.  While your organization may be focused on ‘not developing applications’, every organization must integrate applications, re-factor legacy capabilities, and establish unified, end-to-end information processing.


By choosing an easy to use, enterprise-ready, and API-centric integration platform, every project team can create a high performance, integration environment that reduces integration cost, interoperates across legacy systems, scales to service message traffic, facilitates governance best practices, and exposes APIs to external partners and mobile applications.

Solution Recommendations

Your goal state enterprise integration architecture delivers the following integration capabilities:

  • Connect anything to anything
  • Democratize enterprise integration
  • Lower integration effort and raise integration quality
  • Fit enterprise integration infrastructure into any project
  • Achieve high performance, high availability, elastic scalability and solid stability


Integration Platform Attributes

When evaluating an integration platform, consider the following attributes:

Connect anything to anything

  • Flexibly expose existing applications and services over different protocols and message formats
  • Connect with SaaS applications, legacy back-ends, and mobile devices
  • Easily incorporate powerful routing and transformation logic

Democratize enterprise integration

  • Lower integration tool learning curve
  • Guide teams towards integration best practices
  • Establish and promote master data, standard APIs, and business services
  • Apply standard integration patterns rapidly and efficiently
  • Encourage API adoption by a wider community

Lower integration effort and raise integration quality

  • Use re-usable enterprise integration pattern building blocks
  • Configure rather than code
  • Apply powerful routing, mediation, and transformation capabilities
  • Enforce enterprise security policies and use cases
  • Integrate  identity management and trust frameworks
  • Lower run-time server instances while maintaining transaction per second (TPS) rates

Fit enterprise integration infrastructure into any project

Achieve high performance, high availability, elastic scalability and solid stability

  • Non-blocking IO processing core, yielding higher performance numbers
  • Supports 1000s of concurrent non-blocking HTTP(S) connections per server
  • Pure streaming and on-demand processing of messages


Integration Architecture Components

Integration architecture components to consider include enterprise service bus, API management, governance registry, business activity monitoring,  message brokers, and identity services.

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

API Management

Encourage resource accessibility, resource re-use, and development community expansion.  API Management components enforce service level tiers, provide developer self-service, encourage API branding, enable monetization, and facilitate integration governance best practices (i.e. API versioning, subscription monitoring, capacity management).

Governance Registry

Store development-time and run-time policies, track dependencies, facilitate lifecycle management, encourage team collaboration, and guide the development process.

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.

Message Broker

Exchanges communications asynchronously or publishes messages for timely access by many subscribers.


Recommended Reading

Reshaping Enterprise Architecture Video Presentation

New IT Plan

API and SOA Convergence

API Integration with No Meetings


Open Source SOA or Open Source ESB

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.

Continue reading

ESB use cases driving a successful ESB PoC

An Enterprise Service Bus (ESB) may serve as the cornerstone of your Service Oriented Architecture infrastructure, or you may feel an ESB is unnecessary and cumbersome. Many integration projects contain simple requirements and use cases that warrant including an ESB, integration framework, or alternative platform components in the integration solution. Selecting the appropriate solution mix requires integration reference architecture guidelines that include a comprehensive decision matrix. Team members 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.

Do you have clear architecture, solution, and ESB PoC guidelines describing how your organization can wisely select integration infrastructure components and products?  Successful enterprise architects and solution architects create an integration reference architecture decision framework, ESB use cases, and product selection guidelines containing:

  • ESB use cases driving integration platform component and integration framework selection.
  • Common Request for Proposal (RFP) categories and line items.
  • Tools describing when to include an ESB, integration framework, or alternative integration platform components (i.e. Data Services Server, API Manager, Governance Registry).
Join me for a WSO2 webinar describing ESB use cases, an ESB reference architecture framework, ESB adoption patterns, and ESB PoC success stories.


ESB Comparison

Can an eight year old product category, which is hotly contested by every middleware vendor, deliver unique and differentiating product offerings?   When performing an ESB comparison, 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.   When technical evaluations focus on core performance and quality of service (i.e .reliability, availability, and scalability), proof of concept workloads must closely mirror expected production profiles and the evaluation effort ideally includes vendor participation.

Continue reading

Progress Sonic to Exit Middleware Market

In John Rymer’s recent blog post, Progress Software Lowers Its Sights, he breaks the news that Progress is divesting perceived ‘non-core’ middleware products.  On the selling block are Progress Sonic ESB, Savvion BPM, Actional services management, and FuseSource.  Progress’ recent strategy shift places Sonic ESB, Sonic MQ, and FuseSource implementations at risk of obsolescence.  The list of probable acquirers could mean product termination and forced migration.

Continue reading

How to pick an ESB? An Enterprise Service Bus Evaluation Framework

All Enterprise Service Bus (ESB) products may be used to build and deploy services, encapsulate legacy systems, route messages, transform message formats, and perform protocol mediation.  Many WSO2 prospects ask me ‘What differentiates WSO2 Enterprise Service Bus?’  This blog post shares my perspective and scales the conversation.

Continue reading

ESB and Enterprise Application Integration

Enterprise application integration (EAI) best practices are based on service-oriented architecture (SOA) principles and a flexible, highly capable SOA Platform.   An enterprise service bus (ESB),  API management, governance registry, and identity services are the cornerstones of successful SOA infrastructure platforms.