How to choose the right Integration Framework - Apache Camel (JBoss, Talend), Spring Integration (Pivotal) or Mule ESB? - JavaOne 2013

© Talend 2013 “Spoilt for Choice – How to choose the right Integration Framework” by Kai Wähner
Spoilt for Choice –
Which Integration Framework to choose?
Kai Wähner
kwaehner@talend.com
@KaiWaehner
www.kai-waehner.de
9/25/2013

Consulting
Developing
Coaching
Speaking
Writing
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
Contact
Email: kwaehner@talend.com
Blog: www.kai-waehner.de/blog
Twitter: @KaiWaehner
Social Networks: Xing, LinkedIn
Kai Wähner

Do not reinvent the „integration wheel“!
There are some good frameworks for integration!
Often, an ESB is the better choice!
Key Messages

• Application Integration
• Integration Frameworks
• Spring Integration
• Mule
• Apache Camel
• And the Winner is ...
Agenda

• Applications
• Interfaces
• Technologies
• Products
Growing IT infrastructure everywhere!

Host  Client / Server  SOA  Cloud  Big Data  ...
Heterogeneity

„point-to-point hell“
Spaghetti solutions

All roads
lead to Rome ...
The solution: application integration

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...
}
Writing glue code?

• Standardized Modeling
• Efficient Realization
• Automatic Testing
Wishes for integrators

Enteprise Integration Patterns

Enterprise Integration Patterns

Complexity
of Integration
Enterprise
Service Bus
Integration Suite
Low High
Integration
Framework
Alternatives for application integration

Complexity
of Integration
Enterprise
Service Bus
Integration Suite
Low High
Integration
Framework
Alternatives for application integration
Spring Integration vs. Mule vs. Apache Camel

• Ease of use
• Open source
• Basic concepts / architecture
• Testability
• Commercial support
• Error handling
• Monitoring
• Enterprise readiness
• Developer-centric vs. designer-centric
• Expandability
• Deployment
• Popularity
• Tool support
• Connectivity
• Domain specific language (DSL)
Comparison Criteria

Similarities

Integration
of different
Technologies
Connectivity

Integration vs. vs.
implement
Integration Frameworks

Ease of Use
• One-click-installer
• One product
• One tool
• One runtime
 Makes it easy for development and operations

Internal DSL
„A domain-specific language (DSL) is a programming language or specification
language dedicated to a particular problem domain, a particular problem
representation technique, and / or a particular solution technique.“
Wikipedia
Domain specific language

http://java.dzone.com/articles/apache-camel-integration
(Exemplarily: Apache Camel => Concepts are all the same, only different names)
Architecture

Standalone
OSGi
Application Server
Web Container
Cloud
Spring Container
Deployment

• Maturity
• Transactions
• Concurrency
• Error handling
• Monitoring
• Testability
• Tooling
• Commercial Support
Enterprise readiness

Integration vs. vs.
Common Public
Attribution License (CPAL)
attention:
more restrictive!
Apache License Apache License
Open Source Licensing

vs. vs.
Commercial support
Integration

STS Integration Graph (for Spring Integration) Mule Studio (for Mule ESB)
JBoss Fuse / Switchyard (for Apache Camel) Talend ESB (for Apache Camel)
Tooling

Differences

• Ease of use
• Open source
• Basic concepts / architecture
• Testability
• Commercial support
• Error handling
• Monitoring
• Enterprise readiness
• Developer-centric vs. designer-centric
• Expandability
• Deployment
• Popularity
• Tool support
• Connectivity
• Domain specific language (DSL)
Focus
Comparison Criteria

AMQP
Feed
File
FTP(S)
GemFire
HTTP
TCP
UDP
JDBC
JMS
Mail
MongoDB
Redis
RMI
SFTP
Stream
Twitter
Web Service
XML
XMPP
„Some more“
„most important ones“ available!
easy to create own connectors using a template!
Connectivity

XML
(Not production-ready yet)

Code example (XML DSL)

http://blog.springsource.org/2012/03/05/introducing-spring-integration-scala-dsl/
http://blog.springsource.org/2012/03/05/introducing-spring-integration-scala-dsl/
Code example (Scala DSL)

Spring Integration in Action
Live demo

Tooling: STS Integration Graph

Pro
• Visual designer for Spring Integration flows
• Open source (part of Spring IDE at github)
• Perfect for usage in Spring projects (which use Spring Tool Suite)
• Simple Eclipse plugin – „just Spring Integration“
• Vice versa editing (code generation vs. coding by hand) ??? Or Contra?
Contra
• Simple Eclipse plugin – there are no „ESB add-ons“
• Non-intuitive usability
• Unclear diagrams
• Immature (e.g. missing documentation, problems with code examples)
• No graphical mapper
• No unified platform (data quality, bpm, etc.)
Tooling: STS Integration Graph

Mule ESB

http://www.mulesoft.org/documentation/display/MULE3USER/Embedding+Mule+in+a+Java+Application+or+Webapp
Deployment as web app or standalone

Many further connectors!
Easy to create own connectors
via Maven archetypes!
AS400 Data Queue
Abdera
Amazon SQS
jBPM
CICS CTG
CXF
Email
FTP
Hibernate
HTTP/S
Legs4Mule
IMAP/S
Servlet
SFTP
SMTP/S
SOAP
STDIO
TCP
UDP
VM
XMPP
WebSphere MQ
WSDL
Amazon S3
Authorize.net
Apple Push
Bit.ly
CMIS
CyberSource
Facebook
Flickr
HBase
Magento
Atom
Base64 encoded
Byte arrays
CSV
Encrypted
GZIP
Hex Strings
HTML/ XHTML
Java Objects
JSON
EDI
COBOL Copybook
XML
Connectivity

Some B2B connectors available, especially for:
Connectivity

„OSGi adds another complexity to building
applications. [...] OSGi is a great specification for
middleware vendors, but a terrible specification for the
end user.“
Ross Mason, MuleSoft, November 2010
Missing OSGi support

XML

Code example (XML DSL – no alternative)

Mule in Action
Live demo

Tooling: Mule Studio

Pro
• Visual Designer for Mule Flows
• Visual „live monitoring“
• Intuitive GUI
• Lightweight Tooling
• Graphical mapper (OEM of CloverETL)
• Vice versa editing (code generation vs. coding by hand) ??? Or Contra?
Contra
• Proprietary
• Subscription required for enterprise features (such as monitoring)
• Graphical mapper not really powerful
• No unified platform (integration, bpm, etc.)
Reminder: „Open source“ does NOT mean „for free“!
Tooling: Mule Studio

Many further components!
Easy to create own components
via Maven archetypes
HTTP
FTP
File
XSLT
MQ
JDBC
Akka
TCP
SMTP
RSS
Quartz
jclouds
LDAP
JMS
EJB
AMQP
Atom
AWS
Bean-Validation
CXF
IRC
Jetty
JMX
Lucene
Netty
RMI
SQL
Twitter
MongoDB
Connectivity (by far most connectors!)

Many B2B connectors available (Talend ESB only), for example:
Connectivity

XML

Code example (Java DSL)

Mailing Lists
Forums
Blogs
Articles
Conference talks
ESBs
Professionals
Jobs
Knowledge
Community  Camel rocks!

Apache Camel in Action
Live demo

Spoilt for Choice:
JBoss ESB, Switchyard, JBoss Fuse
Roadmap: http://www.redhat.com/promo/jboss_integration_week/
Tooling: JBoss

Tooling: JBoss Fuse

Pro
• Visual designer for Camel routes
• Visual „live monitoring“ (for debugging, browsing, tracing)
• Intuitive GUI
• Lightweight Tooling
• Now open sourced (after acquisition of Red Hat)
• Vice versa editing (code generation vs. coding by-hand) ??? Or Contra?
Contra
• Unsure future? What happens after Switchyard is production-ready?
• Subscription required for enterprise features (such as monitoring)
• No unified platform (integration, bpm, etc.)
• No graphical mapper
Tooling: JBoss Fuse

Tooling: JBoss Switchyard
Facts
• Will replace JBoss ESB (say it‘s developers)
• Wrapper around Camel + SCA Support
• Not production-ready yet (tooling, support)

Tooling: Talend ESB

Pro
• Visual Designer for Camel routes
• Visual „live monitoring“ (for debugging, browsing, tracing)
• Open source
• GUI palette for Camel components (instead of writing endpoint URIs)
• Zero Coding (you can also write custom code, of course)
• Unified platform (for ESB, DI, BPM, Big Data, Data Quality, MDM)
• Graphical mapping (very powerful including XML, EDI, Cobol, Java, etc.)
Contra
• No vice versa code editing (only code generation) ??? Really a Contra?
• Full ESB, not just Camel tooling (may be bad in a few use cases), therefore not as lightweight
• Subscription required for enterprise features (e.g. monitoring or combination with DQ, BPM, etc.)
Tooling: Talend ESB

Integration
... all three integration frameworks

Integration
When to use which integration framework?

Integration
• Spring Projects
• „Typical“ JVM Technologies
(File, JMS, REST, SOAP, ...)
• No additional Framework wanted

Integration
• One of its B2B connectors is
required (and it is not available
in Camel / Talend)
• If you definitely just need an ESB
in your project, no ETL, DQ,
BPM, etc.

Integration
• Without question, Camel is the best
of these alternatives!
• In all other cases
(largest community, great DSLs,
most connectors, different vendors)

Hmm...
Actually, when should
I use an
integration framework?
... after you have learned the differences

Complexity
of Integration
Enterprise
Service Bus
Integration Suite
Low High
Integration
Framework
INTEGRATION
Connectivity
Routing
Transformation
When to use an integration framework?

Connectivity
Routing
Transformation
INTEGRATION
Tooling
Monitoring
Support
Complexity
of Integration
Enterprise
Service Bus
Integration Suite
Low High
Integration
Framework
+
When to use an Enterprise Service Bus?

Connectivity
Routing
Transformation
Complexity
of Integration
Enterprise
Service Bus
Integration Suite
Low High
Integration
Framework
INTEGRATION
Tooling
Monitoring
Support
+
BUSINESS PROCESS MGT.
BIG DATA / MDM
REGISTRY / REPOSITORY
RULES ENGINE
„YOU NAME IT“
+
When to use an integration suite?

Data
Quality
Data
Integration
MDM ESB
Big
Data
Big Data
 Open source license
 Free of charge
 Optional support
 Based on open source
projects such as
Eclipse or Apache
Camel, CXF, Hadoop
 Commercial license
 Subscription model
 Support included
Data
Quality
Data
Integration MDM ESB BPM
Example: Talend Unified Platform

Open Source
Proprietary
ESB vendor == integration suite vendor?

ESB BPM Data Quality
ESB vendor == integration suite vendor?

• A lot of glue code
• Testing
• Bugfixing
• No support
Some other people already had
the problems you would have!
Custom combination of ESB, BPM, etc.?

Did you get the key messages?

Do not reinvent the „integration wheel“!
There are some good frameworks for integration!
Often, an ESB is the better choice!
Key messages

Thank you for your attention. Questions?
KAI WÄHNER
kwaehner@talend.com
www.kai-waehner.de
LinkedIn / Xing
@KaiWaehner

How to choose the right Integration Framework - Apache Camel (JBoss, Talend), Spring Integration (Pivotal) or Mule ESB? - JavaOne 2013

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (20)

Similar to How to choose the right Integration Framework - Apache Camel (JBoss, Talend), Spring Integration (Pivotal) or Mule ESB? - JavaOne 2013

Similar to How to choose the right Integration Framework - Apache Camel (JBoss, Talend), Spring Integration (Pivotal) or Mule ESB? - JavaOne 2013 (20)

More from Kai Wähner

More from Kai Wähner (20)

Recently uploaded

Recently uploaded (20)

How to choose the right Integration Framework - Apache Camel (JBoss, Talend), Spring Integration (Pivotal) or Mule ESB? - JavaOne 2013