Enterprise Integration Patterns Revisited in 2014

Kai Wähner - Enterprise Integration Patterns Revisited
© Copyright 2000-2014 TIBCO Software Inc.
Enterprise Integration Patterns Revisited
Kai Wähner
kwaehner@tibco.com
@KaiWaehner
www.kai-waehner.de
Xing / LinkedIn  Please connect!

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: kontakt@kai-waehner.de
Blog: www.kai-waehner.de/blog
Twitter: @KaiWaehner
Social Networks: Xing, LinkedIn
Kai Wähner

Key Messages
Do not reinvent the „integration wheel“!
EIPs solve typical integration problems!
There is good tool support for EIPs!

Agenda
– Application Integration
– Enterprise Integration Patterns
– Modeling
– Frameworks and Tools
– Future

• Applications
• Interfaces
• Technologies
• Products
• Cloud
• Mobile
• Internet of Things
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 a lot of Glue Code?

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

“A software design pattern, in the sense of a template, is a
general solution to a problem in programming. A design
pattern provides a reusable architectural outline that may
speed the development of many computer programs.”
http://en.wikipedia.org/wiki/Design_pattern
What is a Design Pattern?

Enterprise Integration Patterns (EIP)

“The goal of EIPs is to document
technology-independent design guidance
that helps developers and architects
describe and develop robust integration
solutions.”
http://www.eaipatterns.com
Enterprise Integration Patterns (EIP)

History of EIPs
• Talk from Gregor Hohpe
– WSO2 Con 2011
– „History, present, future of EIP“
– A lot about past (ideas, creation of book, ...)
– http://www.youtube.com/watch?v=Xwi1DU6KoQ4
• Today‘s Talk
– Not too much about history
– Just about present and future

Status Quo
• Enterprise Integration Patterns do not change
• Just technologies change
• Implementations are already available

EIP Example: Splitter

EIP Example: Aggregator

Combining EIPs shows their true power!
A + B + C = ABC

EIP Example: Composed Message Processor

Enterprise Integration Patterns

Use Case Example

Modeling Tool: Microsoft Visio (Windows)

Modeling Tool: Omnigraffle (Mac)

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
INTEGRATION
Connectivity
Routing
Transformation
When to use an Integration Framework?

Integration
of different
Technologies
Connectivity

Many further connectors
Easy to create own components
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

Integration
implement
Integration Frameworks

Code Example: Apache Camel (Java DSL)

Code Example: Apache Camel (XML DSL)

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?

Enterprise Service Bus (ESB)
Replace point to point integration with a
publish and subscribe
Lay the foundation for a real-time
information architecture
Faster and more predictable
time-to-market
Transform IT into a strategic differentiator
for the business

Enterprise Service Bus (ESB)
Decision
Data
Conversion
Transitions
Process
Call
Process Design Tools
BusinessWorks processes
Connectors to vendor applicationsConnectors to technologies
Connectors
(e.g. JMS, java, FTP) (e.g. SAP, SF.com)
Conversion to XML
Enterprise Integration
Patterns

ESB Example: TIBCO BusinessWorks
Graphical
Process
Modeling
Native
Standards based
XSLT Mapper
Adapters,
Services,
Processes,
Deployment,
Management
Drag-n-Drop
Access to
Resources
Fully Integrated
Test Environment
Intuitive graphical design environment streamlines
time and cost of development and training

ESB Example: TIBCO BusinessWorks

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?

Open Source
Proprietary
ESB Vendor == Integration Suite Vendor?
Watch out!
• All integrated within one product?  Vision!
• Not integrated?  Often reality!
• Loosely coupled, highly integrated?  Best choice!

The Information Bus - SOA / EDA
Modeling, Forms,
Rules, Simulation
Event Processing
Impact analysis
Correlation, Filtering
Event capture
Business Intelligence
Anayltics Historical
Trends
Service Deployment
Java
.NET
Ruby, etc.
Governance
Registry
Repository
Policy Mgmt
Service
Mediation
Web Services
Transformation
Service Routing
Service Orchestration
CSA, Composits, Integration
Custom apps B2B & EDI
Packaged apps ETL
Mainframe MFT
Master Data
Management
Common data repository
„golden record“
Data synch services
Data Governance & Mgmt
Rich
Internet
apps
Web 2.0 AJAX,
GWT, App
Marketplace
Social
Collabo-
ration
FaceBook
Sys Mgmt
&
Monitoring
SNMP
JMX
TIBCO Product Map

The Information Bus - SOA / EDA
Modeling, Forms,
Rules, Simulation
Event Processing
Impact analysis
Correlation, Filtering
Event capture
Business Intelligence
Anayltics Historical
Trends
Service Deployment
Java
.NET
Ruby, etc.
Governance
Registry
Repository
Policy Mgmt
Service
Mediation
Web Services
Transformation
Service Routing
Service Orchestration
CSA, Composits, Integration
Custom apps B2B & EDI
Packaged apps ETL
Mainframe MFT
Master Data
Management
Common data repository
„golden record“
Data synch services
Data Governance & Mgmt
Rich
Internet
apps
Web 2.0 AJAX,
GWT, App
Marketplace
Social
Collabo
ration
FaceBook
Sys Mgmt
&
Monitoring
SNMP
JMX
TIBCO AMX BPM
BusinessStudio
TIBCO
BusinessEvents
ActiveSpaces
TIBCO SpotFire tibbr
Hawk
Service Perform Mgr
TIBCO BusinessWorks
Adapters
Managed File
Transfer
BusinessConnect TIBCO ServiceBus
SOA Registry
Policy Manager
SOA Repository TIBCO ServiceGrid
TIBCO EMS
Enterprise Msg Service
Rendezvous
FTL
Silver Mobile,
BPM Clients
AMX ActiveMatrix
TIBCO CIM
Collaborative
Information Mgr

EIPs are needed everywhere…
… not just in an ESB!
Example
Stream Processing for Real Time Processing of Big Masses of Data ( Fast Data):

ESB Vendor == Integration Suite Vendor?
ESB BPM DQ

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

– Application Integration
– Enterprise Integration Patterns
– Modeling
– Frameworks and Tools
– Future
Agenda

History: “Too Late” Architecture
EVENTS
Mainframe/ERP/DB/App
ACTION
Transaction Based Architectures
Not Elastic, Doesn’t Scale,
“Always Late” architecture and analytics
Typical architecture in the past / legacy
• ETL  „Extract Transform Load“
• Architectures are transaction-based

Today / Future: Real Time Architecture
EVENTS
Mainframe/ERP/DB/App
ACTION
Behavior Based Architectures
Transaction
Data, Event and
Analytics
Elastic, Scales, Real time architecture
(Events, Data and Analytics)
Typical architecture today (at least vision)
• ETL  „Extracted Too Late“
• Messaging and Events: MUST HAVE!
• Real Time  ESB, Stream Processing
• Big Data  Many more Polyglot Data
Sources
• Fast Data  In-Memory Computing

Future of EIPs: The BAD News
• New Patterns (since release of the book)?  NOT YET
– Conversations
– Complex Event Processing
– Error Handling
• More Details: „EIP Visions“  TO BE DETERMINED
– EIP I: Messaging  done
– EIP II: Conversations  50 page paper
– EIP III: Process  tbd
– EIP IV: Event Processing  tbd
http://www.eaipatterns.com/ramblings/72_eipvolumes.html

Future of EIPs: The GOOD News
• New Patterns not necessary!  OFTEN
– EIPs were based on Messaging already, which is a good thing (usually)
– Conversations == State == Anti Pattern (often)
– Integration scenarios can be solved with existing patterns (usually)
• Better Tooling  YES
– More frameworks and products (e.g. Stream Processing)
– More stability
– Ease of use (no coding)

Complementary: SOA Design Patterns
• Patterns for performance, scalability,
and availability
• Security and manageability patterns
• Message exchange patterns
• Service consumer patterns
• Service integration patterns

Future of Integration
Integration will get even more important in
the future than it is today!
The number of different data sources and technologies increases
even more than in the past
– CRM, ERP, Host, B2B, etc. will not disappear
– DWH, Hadoop cluster, event / streaming server, In-Memory
DB – all of them have to communicate
– Cloud, Mobile, Internet of Things are no option, but our
future!
Buy this book
if you do not own it already!

Did you get the Key Message?

Do not reinvent the „integration wheel“!
EIPs solve typical integration problems!
There is good tool support for EIPs!
Recap: Key Messages

Questions?
Kai Wähner
kwaehner@tibco.com
@KaiWaehner
www.kai-waehner.de
Xing / LinkedIn  Please connect!

Enterprise Integration Patterns Revisited in 2014

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Mehr von Kai Wähner

Mehr von Kai Wähner (20)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

Enterprise Integration Patterns Revisited in 2014