Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Colombo Architecture Meetup - Enterprise Architectural Challenges in Large Enterprises

816 views

Published on

Published in: Technology

Colombo Architecture Meetup - Enterprise Architectural Challenges in Large Enterprises

  1. 1. Colombo Architecture Meetup Enterprise Integration Architectural Challenges in Large Enterprises By Crishantha Nanayakkara Head of Technology, ICTA
  2. 2. Vs
  3. 3. 3 EnterpriseEnterprise ApplicationApplication IntegrationIntegration
  4. 4. 4 The Information Silos Systems that are not connected Drawbacks: ● Isolated without insufficient communication to the rest of the world
  5. 5. 5 The Enterprise Integration Benefits: ● Provides a way to connect each other Drawbacks: ● Extremely “Spaghetti” like architecture, create headaches
  6. 6. The Enterprise Integration
  7. 7. 7 EnterpriseEnterprise ApplicationApplication IntegrationIntegration ArchitecturalArchitectural ChallengesChallenges
  8. 8. 8 ● Integration ● Reliability ● Mediation ● Service Orientation ● Interoperability ● Security ● Federated Identity
  9. 9. 9 1. Integration1. Integration
  10. 10. 10 Point-to-Point Integration
  11. 11. 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. 12. 12 Point-to-Point Integration ● The value of the network increases linearly over time while its costs increase exponentially
  13. 13. 13 The Solution A more centralized approached to the previous point-to-point approach The Solution
  14. 14. 14 2. Reliability2. Reliability
  15. 15. 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. 16. 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. 17. 17 3. Mediation3. Mediation
  18. 18. 18
  19. 19. 19 Enterprise Integration Patterns
  20. 20. 20 Enterprise Integration Patterns Message Router Pipes and Filters
  21. 21. 21 Enterprise Integration Patterns Content Based Router Message Translator
  22. 22. 22 Enterprise Integration Patterns Message Filter Message Splitter
  23. 23. 23 Enterprise Integration Patterns Message Aggregator Message Resequencer
  24. 24. 24 Source: http://www.idevnews.com/views/images/uploads/general/talend_intfactory.jpg Enterprise Integration Patterns
  25. 25. 25 The integrated SOLUTION
  26. 26. 26 5. Service5. Service OrientationOrientation
  27. 27. 27 The SOA Environment Source: Open Source SOA
  28. 28. 28 A typical SOA environment ● Service Interfaces/ Contracts ● Service Transparency ● Service Composition ● Service Registry or Publication ● Service Governance
  29. 29. 29 The Core Characteristics of SOA 1) The Service Interface / Contract
  30. 30. 30 The Core Characteristics of SOA 2) The Service Transparency What if you change the IP of this address???
  31. 31. 31 The Core Characteristics of SOA 2) The Service Transparency
  32. 32. 32 The Core Characteristics of SOA 3) 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. 33 The Core Characteristics of SOA 3) Service Composition
  34. 34. 34 The Technologies of SOA
  35. 35. 35 Bottom Up Vs Contract First ● Why Contract First is better?
  36. 36. 36 6. Interoperability6. Interoperability
  37. 37. 37 Private Sector Companies Services Application Services 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. 38. 38 DMTDMT Translation in the Middleware Translation in the Middleware WPDMTWPDMT Owner First Name Owner Last Name Owner Address Line1 Owner Address Line2 Owner City Vehicle Reg No Fuel Type Weight Number of Seats Owner First Name Owner Last Name Owner Address Line1 Owner Address Line2 Owner City Vehicle Reg No Fuel Type Weight Number of Seats Owner Full Name Owner Address Vehicle Reg No Fuel Type Weight Number of Seats Owner Full Name Owner Address Vehicle Reg No Fuel Type Weight Number of Seats
  39. 39. 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. 40. 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. 41. 41 Interoperability Frameworks
  42. 42. 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. 43. 43 Enterprise Architecture Frameworks (EAF)
  44. 44. 44 7. Security7. Security
  45. 45. 45 Transport Vs Message Level Security
  46. 46. 46 Point to Point Security ESB as a Security Gateway
  47. 47. 47 End to End Security with Pass Through
  48. 48. 48 End to End Security with Security Translantion at ESB Level
  49. 49. 49 Web Services Security Stack Reference: Securing Web Services with WS-Security (Jothy Rsenberg, David L Remy)
  50. 50. 50 8. Federated Identity8. Federated Identity
  51. 51. 51 ● SAML provides a loosely coupled identity management with the help of WS-Trust and WS- Fedeartion specifications.
  52. 52. 52

×