Spoilt for Choice: How to Choose the Right Enterprise Service Bus (ESB)?

Spoilt for Choice –
How to choose the right Enterprise Service Bus
Kai Wähner, Principal Consultant

Kai Wähner

Main Tasks
Requirements Engineering
Enterprise Architecture Management
Business Process Management
Architecture and Development of Applications
Service-oriented Architecture
Integration of Legacy Applications
Cloud Computing
Big Data

Consulting Contact
Developing Email: kwaehner@talend.com
Coaching Blog: www.kai-waehner.de/blog
Speaking Twitter: @KaiWaehner
Writing Social Networks: Xing, LinkedIn

© Talend 2011 2

Key messages

There is no silver bullet for integration!
A product named ‘ESB’ is often the wrong choice!

Choosing the right integration solution is essential for project success!

© Talend 2011 "Spoilt for Choice - How to choose the right Enterprise Service Bus" by Kai Wähner - OOP 2013 3

Agenda

 What is the Problem of Systems Integration?
 What is an Enterprise Service Bus?
 What are the Comparison Criterias?
 When to use an Integration Framework?
 When to use an Enterprise Service Bus?
 When to use an Integration Suite?
 What is the Conclusion?


Agenda


Live Demos


Agenda



What is the problem of systems integration?

• Applications
• Interfaces
• Technologies
• Products



„Spaghetti communication“


All roads lead to Rome...


How to solve the problem?

• Standardized Modeling
• Efficient Realization
• Automatic Testing


How to solve the problem?

Hmm, I need an
Enterprise Service Bus,
right?


Agenda



What is an Enterprise Service Bus (ESB)?

There is no standard definition! 

Always define what you mean, when you say „ESB“!

For this talk, we just say: „An ESB helps for systems integration“ –
because we look at so many different THINGS which are called ESB

For this talk, an ESB is a product (beyond APIs or REST / SOAP calls),
which offers an „infrastructure“ for routing, transformation, security,
etc.

If you think you need an ESB, you should always think about integration
frameworks and integration suites. Choose the right one!



Enterprise Integration Suite
Integration Service Bus
Framework
Complexity
of Integration
Low High

Includes Includes


Agenda



Comparison Criterias

• Ease of Use
• Maintainability and Monitoring
• Community
• Enterprise Support
• Functionality
• Flexibility
• Extensibility
• Standards rating
• Connectors positive
• Costs medium
• Licencing negative


You will NOT get a comparison matrix for ESB products 

• Too many different features to compare!
• Too many different concepts to compare!
• Almost impossible to keep it up-to-date!
• Almost impossible to create it unbiased!


What you will get ...

... is an answer to the question:
• if you need an integration framework, an ESB, or a suite!
• if you need a proprietary or open source solution!
• how to get a short list of alternatives!


Agenda



What is an Integration Framework?

Framework
Complexity
of Integration
Low High

INTEGRATION
Connectivity
Routing
Transformation

Integration Frameworks

Integration


Enterprise Integration Patterns


Deployment

Standalone
Spring
Cloud Container

Web Container

Application
Server

Writing glue code? (example: AWS S3 with Java)
AmazonS3 s3 = new AmazonS3Client(new PropertiesCredentials(
S3Sample.class.getResourceAsStream("AwsCredentials.properties")));

String bucketName = "my-first-s3-bucket-" + UUID.randomUUID();
String key = "MyObjectKey";

try {

s3.createBucket(bucketName);
s3.putObject(new PutObjectRequest(bucketName, key, createSampleFile()));

S3Object object = s3.getObject(new GetObjectRequest(bucketName, key));

ObjectListing objectListing = s3.listObjects(new ListObjectsRequest()
.withBucketName(bucketName)
.withPrefix("My"));

s3.deleteObject(bucketName, key);
s3.deleteBucket(bucketName);

} catch (AmazonServiceException ase) {
// error handling...
} catch (AmazonClientException ace) {
// error handling...
}


Domain Specific Language (example: Apache Camel)

// Producer
from(“ftp:toS3")
.setHeader(S3Constants.KEY, simple(“order.txt"))
.to("aws-s3://myBucket?accessKey=" + a+ "&secretKey= " + s)

// Consumer
from(„salesforce://orders__c?user=dummy1“)
.to(“ibm-database:orderData")


Domain Specific Language (example: Apache Camel)


Live Demo

Integration Framework in Action...

Comparison Criterias (Integration Framework)
Criteria Proprietary Open Source

Ease of use N.A. Learn the framework API and internals

Maintainability and N.A. Examine and maintain code, not much tooling besides IDE
Monitoring

Community N.A. Bugtracker, Mailing List, Forum, Articles, Blog Posts, Conferences

Enterprise Support N.A. Some consulting, no enterprise support for production

Functionality N.A. Most important integration features implemented (e.g. EIPs), tooling
missing for administration and monitoring
Flexibility N.A. Open Source, change what you want

Extensibility N.A. Standards-based, defacto Standards

Connectors N.A. Many technical adapters available, but none for direct integration of
business products

Costs N.A. For free, Open Source

Licencing N.A. Do whatever you want with it (usually Apache Licence)


Agenda




Framework
Complexity
of Integration
Low High

INTEGRATION
Connectivity Tooling
Routing
© Talend 2011
+
Monitoring
Support
Transformation "Spoilt for Choice - How to choose the right Enterprise Service Bus" by Kai Wähner - OOP 2013 31

ESB Vendors – Gartner Quadrant 2012


Mule ESB


Talend ESB


RedHat / JBoss + acquisitions

Good products, awesome community ... but:

Three ESBs (JBoss ESB, Switchyard, Fuse ESB)
Two BPMs (jBPM, Polymita)
No unified platform (yet)

© Talend 2011 35

Oracle ESB

Source: http://www.slideshare.net/gschmutz/oracle-soa-suite-11g-mediator-vs-oracle-service-bus-osb

© Talend 2011 36

Oracle ESB

Source: http://www.slideshare.net/gschmutz/oracle-soa-suite-11g-mediator-vs-oracle-service-bus-osb

© Talend 2011 37

Three IBM ESBs

© Talend 2011 38

Live Demo

Enterprise Service Bus in Action...

Comparison Criterias (Enterprise Service Bus)
Ease of use Complex installation (consultants needed !?), One Click Installer (also for Mac), start using
„tool hell“ after minutes

Maintainability and Really powerful tooling (e.g. for administration A little bit tooling (e.g. for administration and
Monitoring and monitoring), maintain in GUI monitoring), maintain in GUI
Community Buy support, many knowledge worldwide, Based on open source projects, plus own
forums (but no real community which helps) community

Enterprise Support 24/7 enterprise support, SLAs as you wish, 24/7 enterprise support, less guarantees than
deployments with thousands of servers proprietary support, check for local consulting
and support
Functionality Integration features Integration features

Flexibility (Make change request + wait long + pay) OR (pay Open source, change what you want
a lot + get it quickly)

Extensibility Do it yourself (often tough) OR pay Standards-based, defacto Standards

Connectors Adapters for technologies and business products Adapters for technologies and business products

Costs MUCH (and even more) LESS (however, be aware that „open source“
does not mean „for free“)
Licencing Complex price list, pay for everything Subscription model, upgrades inclusive,
(upgrades, migration to VM, „you-name-it“) predictive costs, downgrades possible

Agenda



What is an Integration Suite?

Framework
Complexity
of Integration
Low High

BUSINESS PROCESS MGT.
INTEGRATION BIG DATA / MDM
Connectivity Tooling REGISTRY / REPOSITORY
Routing
Transformation
+ Monitoring
Support
+ RULES ENGINE
„YOU NAME IT“

Talend Unified Platform

Data Data
Big Data Quality Integration MDM ESB BPM

 Commercial license
 Subscription model
 Support included

 Open source license
 Free of charge
 Optional support
Big Data Data
Data Quality Integration
MDM ESB

 Based on open source
projects such as
Eclipse or Apache
Camel, CXF, Hadoop

© Talend 2011 46

Live Demo

Integration Suite in Action...

ESB Vendor == Integration Suite Vendor ???

Proprietary

Open Source


ESB Vendor == Integration Suite Vendor ???

ESB BPM Big Data

Custom combination of ESB, BPM, Big Data, etc.?

• A lot of glue code
• Testing
• Bugfixing
• No support

Some other people already had
the problems you would have!


Comparison Criterias (Integration Suite)
Ease of use Even more complex installation (consultants One Click Installer (also for Mac), start using
needed !?), „tool hell“ after minutes, unified platform

Maintainability and Powerful tooling (e.g. for administration and A little bit tooling (e.g. for administration and
Monitoring monitoring), maintain in GUI monitoring), maintain in GUI
Community Buy support, forums (but no real community Based on open source projects, plus own
which helps) community

deployments with thousands of servers proprietary support, check for local consulting
and support
Functionality Integration features + many more (BAM, CEP, Integration features + some more
EDA, etc., etc., etc.)
Flexibility (Make change request + wait long + pay) OR (pay Open source, change what you want
a lot + get it quickly)

Extensibility Do it yourself (tough) OR pay Standards-based, defacto Standards


Costs MUCH (and even more) LESS (however, be aware that „open source“
does not mean „for free“)
Licencing Complex price list, pay for everything Subscription model, upgrades inclusive,
(upgrades, migration to VM, „you-name-it“) predictive costs, downgrades possible

One last word regarding functionalities and features...


Ease of use Even more complex installation (consultants needed One Click Installer (also for Mac), start using after
!?), „tool hell“ minutes, unified platform

Maintainability and Powerful tooling (e.g. for administration and A little bit tooling (e.g. for administration and

Main arguments
Monitoring monitoring), maintain in GUI monitoring), maintain in GUI

Community Buy support, forums (but no real community which Based on open source projects, plus own community

for proprietary
helps)

solutions! deployments with thousands of servers proprietary support, check for local consulting and
support

Functionality Integration features + many more (BAM, CEP, EDA, Integration features + some more
etc., etc., etc.)

(but be sure that Flexibility (Make change request + wait long + pay) OR (pay a
lot + get it quickly)
Open source, change what you want

you really need it) Extensibility Do it yourself (tough) OR pay Standards-based, defacto Standards


Costs MUCH (and even more) LESS

Licencing Complex price list, pay for everything (upgrades, Subscription model, upgrades inclusive, predictive
migration to VM, „you-name-it“) costs, downgrades possible


Agenda



How to continue?

• 1) Decide if you need a framework, an ESB, or a suite!
• 2) Decide if you need an open source or proprietary solution!
• 3) Evaluate your short list!
• 4) Do proof of concepts by yourself – not by vendor consultants!
• 5) Choose the right tool for the right job!


Did you get the key message?


Key messages

There is no silver bullet for integration!
A product named ‘ESB’ is often the wrong choice!

Choosing the right integration solution is essential for project success!


Did you get the key message?


Thank you for your attention. Questions?

KAI WÄHNER
kwaehner@talend.com
www.kai-waehner.de
LinkedIn / Xing
@KaiWaehner

Spoilt for Choice: How to Choose the Right Enterprise Service Bus (ESB)?

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (12)

Similar to Spoilt for Choice: How to Choose the Right Enterprise Service Bus (ESB)?

Similar to Spoilt for Choice: How to Choose the Right Enterprise Service Bus (ESB)? (20)

More from Kai Wähner

More from Kai Wähner (20)

Recently uploaded

Recently uploaded (20)

Spoilt for Choice: How to Choose the Right Enterprise Service Bus (ESB)?