Enterprise Integration Zone is brought to you in partnership with:

As VP of Technology Evangelism at WSO2, Chris Haddad raises awareness of Platform as a Service, Cloud Architecture, Service Oriented Architecture, API Management, and Enterprise Integration. Prior to joining WSO2, Haddad’s experience includes building software development teams, contributing to open source, crafting technology roadmaps, leading Gartner research teams, and delivering Software as a Service and Web applications. Chris is a DZone MVB and is not an employee of DZone and has posted 107 posts at DZone. You can read more from them at their website. View Full User Profile

Re-shaping Your Enterprise Integration Architecture

10.04.2013
| 4516 views |
  • submit to reddit

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.

Analysis

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.

Published at DZone with permission of Chris Haddad, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)