Embed Size (px)
Citation preview
Colombo Architecture Meetup
Enterprise Integration ArchitecturalChallenges in Large Enterprises
By Crishantha NanayakkaraHead of Technology, ICTA
Vs
3
Enterprise Enterprise Application Application IntegrationIntegration
4
The Information Silos
Systems that are not connected
Drawbacks:● Isolated without insufficient communication to the rest of the world
5
The Enterprise Integration
Benefits:● Provides a way to connect each other
Drawbacks:● Extremely “Spaghetti” like architecture, create headaches
The Enterprise Integration
7
Enterprise Enterprise Application Application Integration Integration
Architectural Architectural ChallengesChallenges
8
● Integration● Reliability● Mediation● Service Orientation● Interoperability● Security● Federated Identity
9
1. Integration1. Integration
10
Point-to-Point Integration
11
Point-to-Point Integration
Specifically, linking every component to every other component will require N(N-1)/2 physical connections
N = Total Number of Components in the Network
e.g: If there are 10 components in the network,
Total number of physical connections = 10 (10-1)/2
= 45
12
Point-to-Point Integration
● The value of the network increases linearly over time while its costs increase exponentially
13
The SolutionA more centralized approached to the previous point-to-point approach
The Solution
14
2. Reliability2. Reliability
15
● This creates a loosely-coupled distributed system, which can continue to function reliably, without downtime, even when individual components or connections fail
Message Oriented Middleware
16
● Supports Remote Communications● Integrating different language/platforms as a
Message Bus (Message Bus Pattern)● Supports Asynchronous Communication● Supports Throttling ● More reliable● Can be used for disconnected operations● Supports mediation
Message Oriented Middleware
17
3. Mediation3. Mediation
18
19
Enterprise Integration Patterns
20
Enterprise Integration Patterns
Message Router
Pipes and Filters
21
Enterprise Integration Patterns
Content Based Router
Message Translator
22
Enterprise Integration Patterns
Message Filter
Message Splitter
23
Enterprise Integration Patterns
Message Aggregator
Message Resequencer
24
Source: http://www.idevnews.com/views/images/uploads/general/talend_intfactory.jpg
Enterprise Integration Patterns
25
The integrated SOLUTION
26
5. Service 5. Service OrientationOrientation
27
The SOA Environment
Source: Open Source SOA
28
A typical SOA environment
● Service Interfaces/ Contracts● Service Transparency● Service Composition● Service Registry or Publication● Service Governance
29
The Core Characteristics of SOA1) The Service Interface / Contract
30
The Core Characteristics of SOA2) The Service Transparency What if you change
the IP of this address???
31
The Core Characteristics of SOA2) The Service Transparency
32
The Core Characteristics of SOA3) Service Composition
– There are two general types of composite services● Simple● Complex
– Simple: Simply wraps one or more lowerlevel services together into a more coarsegrained operation
– Complex: (Work Flow Type BPM)● WSBPEL● Entry Point of invoking WSBPEL is usally a web
service
33
The Core Characteristics of SOA3) Service Composition
34
The Technologies of SOA
35
Bottom Up Vs Contract First
● Why Contract First is better?
36
6. Interoperability6. Interoperability
37
Private Sector Companies
Services
ApplicationServices
Application
The Department of Motor Traffic
Vehicle Domain
Services
Application
The Department Registration of Persons
Personal Domain
Services
Application
The Land Ministry
Land Domain
38
DMTDMT
Translationin the
Middleware
Translationin the
Middleware
WPDMTWPDMT
Owner First NameOwner Last NameOwner Address Line1Owner Address Line2Owner CityVehicle Reg NoFuel TypeWeightNumber of Seats
Owner First NameOwner Last NameOwner Address Line1Owner Address Line2Owner CityVehicle Reg NoFuel TypeWeightNumber of Seats
Owner Full NameOwner AddressVehicle Reg NoFuel TypeWeightNumber of Seats
Owner Full NameOwner AddressVehicle Reg NoFuel TypeWeightNumber of Seats
39
The Need
● So many distributed & diverse systems,
– May have used various technologies
– May have used various data architectures
– May have used conflicting policies, procedures, guidelines
40
The Solution
● Standardize data representation, formats and semantics on the wire by having an Interoperability Framework
● Use Open Standards
Services Oriented Architecture&
Web Services
41
Interoperability Frameworks
42
Enterprise Architecture
● Enterprise Architecture is the complete expression of the enterprise
● “Enterprise Architecture is about understanding all of the different elements that go to make up the enterprise and how those elements interrelate.” - The Open Group
43
Enterprise Architecture Frameworks (EAF)
44
7. Security7. Security
45
Transport Vs Message Level Security
46
Point to Point SecurityESB as a Security Gateway
47
End to End Securitywith Pass Through
48
End to End Security with Security Translantion at ESB Level
49
Web Services Security Stack
Reference: Securing Web Services with WS-Security (Jothy Rsenberg, David L Remy)
50
8. Federated Identity8. Federated Identity
51
● SAML provides a loosely coupled identity management with the help of WS-Trust and WS-Fedeartion specifications.
52
