Your SlideShare is downloading. ×
0
Colombo Architecture MeetupEnterprise Integration ArchitecturalChallenges in Large EnterprisesBy Crishantha NanayakkaraHea...
Vs
3EnterpriseEnterpriseApplicationApplicationIntegrationIntegration
4The Information SilosSystems that are not connectedDrawbacks:● Isolated without insufficientcommunication to the rest of ...
5The Enterprise IntegrationBenefits:● Provides a way to connect eachotherDrawbacks:● Extremely “Spaghetti” likearchitectur...
The Enterprise Integration
7EnterpriseEnterpriseApplicationApplicationIntegrationIntegrationArchitecturalArchitecturalChallengesChallenges
8● Integration● Reliability● Mediation● Service Orientation● Interoperability● Security● Federated Identity
91. Integration1. Integration
10Point-to-Point Integration
11Point-to-Point IntegrationSpecifically, linking every component to every othercomponent will require N(N-1)/2 physical c...
12Point-to-Point Integration● The value of the network increases linearly over timewhile its costs increase exponentially
13The SolutionA more centralized approached to the previous point-to-point approachThe Solution
142. Reliability2. Reliability
15● This creates a loosely-coupled distributed system,which can continue to function reliably, withoutdowntime, even when ...
16● Supports Remote Communications● Integrating different language/platforms as aMessage Bus (Message Bus Pattern)● Suppor...
173. Mediation3. Mediation
18
19Enterprise Integration Patterns
20Enterprise Integration PatternsMessage RouterPipes and Filters
21Enterprise Integration PatternsContent Based RouterMessage Translator
22Enterprise Integration PatternsMessage FilterMessage Splitter
23Enterprise Integration PatternsMessage AggregatorMessage Resequencer
24Source: http://www.idevnews.com/views/images/uploads/general/talend_intfactory.jpgEnterprise Integration Patterns
25The integrated SOLUTION
265. Service5. ServiceOrientationOrientation
27The SOA EnvironmentSource: Open Source SOA
28A typical SOA environment● Service Interfaces/ Contracts● Service Transparency● Service Composition● Service Registry or...
29The Core Characteristics of SOA1) The Service Interface / Contract
30The Core Characteristics of SOA2) The Service Transparency What if you changethe IP of thisaddress???
31The Core Characteristics of SOA2) The Service Transparency
32The Core Characteristics of SOA3) Service Composition– There are two general types of composite services● Simple● Comple...
33The Core Characteristics of SOA3) Service Composition
34The Technologies of SOA
35Bottom Up Vs Contract First● Why Contract First is better?
366. Interoperability6. Interoperability
37Private Sector CompaniesServicesApplicationServicesApplicationThe Department of Motor TrafficVehicle DomainServicesAppli...
38DMTDMTTranslationintheMiddlewareTranslationintheMiddlewareWPDMTWPDMTOwner First NameOwner Last NameOwner Address Line1Ow...
39The Need● So many distributed & diverse systems,– May have used various technologies– May have used various data archite...
40The Solution● Standardize data representation, formats andsemantics on the wire by having anInteroperability Framework● ...
41Interoperability Frameworks
42Enterprise Architecture● Enterprise Architecture is the completeexpression of the enterprise● “Enterprise Architecture i...
43Enterprise ArchitectureFrameworks (EAF)
447. Security7. Security
45Transport Vs Message LevelSecurity
46Point to Point SecurityESB as a Security Gateway
47End to End Securitywith Pass Through
48End to End Securitywith Security Translantion at ESB Level
49Web Services Security StackReference: Securing Web Services with WS-Security (Jothy Rsenberg, David L Remy)
508. Federated Identity8. Federated Identity
51● SAML provides a loosely coupled identitymanagement with the help of WS-Trust and WS-Fedeartion specifications.
52
Upcoming SlideShare
Loading in...5
×

Enterprise Integration Architectural Challenges in Large Enterprises - Colombo Architecture Meetup - Session-02

115

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
115
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
9
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "Enterprise Integration Architectural Challenges in Large Enterprises - Colombo Architecture Meetup - Session-02"

  1. 1. Colombo Architecture MeetupEnterprise Integration ArchitecturalChallenges in Large EnterprisesBy Crishantha NanayakkaraHead of Technology, ICTA
  2. 2. Vs
  3. 3. 3EnterpriseEnterpriseApplicationApplicationIntegrationIntegration
  4. 4. 4The Information SilosSystems that are not connectedDrawbacks:● Isolated without insufficientcommunication to the rest of theworld
  5. 5. 5The Enterprise IntegrationBenefits:● Provides a way to connect eachotherDrawbacks:● Extremely “Spaghetti” likearchitecture, create headaches
  6. 6. The Enterprise Integration
  7. 7. 7EnterpriseEnterpriseApplicationApplicationIntegrationIntegrationArchitecturalArchitecturalChallengesChallenges
  8. 8. 8● Integration● Reliability● Mediation● Service Orientation● Interoperability● Security● Federated Identity
  9. 9. 91. Integration1. Integration
  10. 10. 10Point-to-Point Integration
  11. 11. 11Point-to-Point IntegrationSpecifically, linking every component to every othercomponent will require N(N-1)/2 physical connectionsN = Total Number of Components in the Networke.g: If there are 10 components in the network,Total number of physical connections = 10 (10-1)/2= 45
  12. 12. 12Point-to-Point Integration● The value of the network increases linearly over timewhile its costs increase exponentially
  13. 13. 13The SolutionA more centralized approached to the previous point-to-point approachThe Solution
  14. 14. 142. Reliability2. Reliability
  15. 15. 15● This creates a loosely-coupled distributed system,which can continue to function reliably, withoutdowntime, even when individual components orconnections failMessage Oriented Middleware
  16. 16. 16● Supports Remote Communications● Integrating different language/platforms as aMessage Bus (Message Bus Pattern)● Supports Asynchronous Communication● Supports Throttling● More reliable● Can be used for disconnected operations● Supports mediationMessage Oriented Middleware
  17. 17. 173. Mediation3. Mediation
  18. 18. 18
  19. 19. 19Enterprise Integration Patterns
  20. 20. 20Enterprise Integration PatternsMessage RouterPipes and Filters
  21. 21. 21Enterprise Integration PatternsContent Based RouterMessage Translator
  22. 22. 22Enterprise Integration PatternsMessage FilterMessage Splitter
  23. 23. 23Enterprise Integration PatternsMessage AggregatorMessage Resequencer
  24. 24. 24Source: http://www.idevnews.com/views/images/uploads/general/talend_intfactory.jpgEnterprise Integration Patterns
  25. 25. 25The integrated SOLUTION
  26. 26. 265. Service5. ServiceOrientationOrientation
  27. 27. 27The SOA EnvironmentSource: Open Source SOA
  28. 28. 28A typical SOA environment● Service Interfaces/ Contracts● Service Transparency● Service Composition● Service Registry or Publication● Service Governance
  29. 29. 29The Core Characteristics of SOA1) The Service Interface / Contract
  30. 30. 30The Core Characteristics of SOA2) The Service Transparency What if you changethe IP of thisaddress???
  31. 31. 31The Core Characteristics of SOA2) The Service Transparency
  32. 32. 32The Core Characteristics of SOA3) Service Composition– There are two general types of composite services● Simple● Complex– Simple: Simply wraps one or more lower­level services together into a more coarse­grained operation– Complex: (Work Flow Type BPM)● WS­BPEL● Entry Point of invoking WS­BPEL is usally a web service
  33. 33. 33The Core Characteristics of SOA3) Service Composition
  34. 34. 34The Technologies of SOA
  35. 35. 35Bottom Up Vs Contract First● Why Contract First is better?
  36. 36. 366. Interoperability6. Interoperability
  37. 37. 37Private Sector CompaniesServicesApplicationServicesApplicationThe Department of Motor TrafficVehicle DomainServicesApplicationThe Department Registration of PersonsPersonal DomainServicesApplicationThe Land MinistryLand Domain
  38. 38. 38DMTDMTTranslationintheMiddlewareTranslationintheMiddlewareWPDMTWPDMTOwner First NameOwner Last NameOwner Address Line1Owner Address Line2Owner CityVehicle Reg NoFuel TypeWeightNumber of SeatsOwner First NameOwner Last NameOwner Address Line1Owner Address Line2Owner CityVehicle Reg NoFuel TypeWeightNumber of SeatsOwner Full NameOwner AddressVehicle Reg NoFuel TypeWeightNumber of SeatsOwner Full NameOwner AddressVehicle Reg NoFuel TypeWeightNumber of Seats
  39. 39. 39The 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. 40. 40The Solution● Standardize data representation, formats andsemantics on the wire by having anInteroperability Framework● Use Open StandardsServices Oriented Architecture&Web Services
  41. 41. 41Interoperability Frameworks
  42. 42. 42Enterprise Architecture● Enterprise Architecture is the completeexpression of the enterprise● “Enterprise Architecture is aboutunderstanding all of the different elementsthat go to make up the enterprise and howthose elements interrelate.” - The OpenGroup
  43. 43. 43Enterprise ArchitectureFrameworks (EAF)
  44. 44. 447. Security7. Security
  45. 45. 45Transport Vs Message LevelSecurity
  46. 46. 46Point to Point SecurityESB as a Security Gateway
  47. 47. 47End to End Securitywith Pass Through
  48. 48. 48End to End Securitywith Security Translantion at ESB Level
  49. 49. 49Web Services Security StackReference: Securing Web Services with WS-Security (Jothy Rsenberg, David L Remy)
  50. 50. 508. Federated Identity8. Federated Identity
  51. 51. 51● SAML provides a loosely coupled identitymanagement with the help of WS-Trust and WS-Fedeartion specifications.
  52. 52. 52
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×