How would ESBs look like, if they were done today.
•
12 likes•11,425 views
ESBs would look different if built today. Large monolithic applications would be decomposed into microservices with bounded contexts. Services would be independently deployable and designed for failure. An ESB centralized integration but microservices use decentralized approaches like service discovery. While challenging, microservices evolve legacy systems towards modular, scalable architectures. It's a learning process, and the industry is still evolving effective patterns.
Report
Share
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to How would ESBs look like, if they were done today.
Similar to How would ESBs look like, if they were done today. (20)
More from Markus Eisele
More from Markus Eisele (17)
Recently uploaded
Recently uploaded (20)
How would ESBs look like, if they were done today.
- 1. 1 How would ESBs look like, if they were done today? Markus Eisele, @myfear Developer Advocate markus@jboss.org October, 2015
- 2. “What’s right isn’t always popular. What’s popular isn’t always right” Howard Cosell
- 3. Application Server Large Java EE / J2EE based applications Application Server EAR EAR EAR WAR JAR JAR JAR JAR JAR JAR WAR JAR JAR EAM <?> LoadBalancer
- 4. • Monolithic application – everything is package into a single .ear • Reuse primarily by sharing .jars • A “big” push to production once or twice a year • Single database schema for the entire application • >= 500k loc • >= Heavyweight Infrastructure • Thousands of Testcases • Barely New Testcases TechnicalImplications
- 5. 5 • >= 20 Team Member • The single .ear requiring a multi-month test cycle / • Huge bug and feature databases • User Acceptance Undefined • Technical Design Approach • Barely Business Components or Domains • Requiring multiple team involvement & significant oversight TeamandQAImplications
- 6. 6 • Still changing requirements. • New features tend to be HUGE! • Cross-cutting concerns nearly impossible to implement. Andevennow…
- 7. 7 Why?
- 8. 8 Technical Dept! We’re lazy! Inexperienced! No education! Outdated Infrastructure! We always did it like that. Outdated Designpattern? Grown application Outdated Runtimes!
- 9. 9 Where did we go from here?
- 10. 10 We treated everything as a legacy system and try to solve integration problems.
- 11. 11 ENTERPRISE! CENTRALIZE! STANDARDS! LICENSES! INTEGRATION? Enterprise Service Bus Orchestration
- 12. 12 • Still very large codebases • Overloaded IDEs • Hard to understand and modify • Hard to test • Complex dependencies • Small Changes generate big Impact • Difficult to scale • Mostly not rewritten but “re-wired” • Data Segmentation not defined • Scaling difficult TechnicalImplications
- 13. 13 Hmmm … and where are we today?
- 14. 14
- 15. 15 Name it whatever you like.
- 16. 16 We’re decomposing monoliths and evolve them into microservices architectures.
- 17. 17 Reduce Impact of Change by Encapsulating Source of Change http://martinfowler.com/articles/microservices.html
- 18. 18 How to find the Right Services?
- 19. 19 Domain Driven Design Bounded contexts Designed For Automation Designed for Failure Independently Deployable FromScratch
- 20. 20 Verb or Use Case e.g. Checkout UI Noun e.g. Catalog product service Single Responsible Principle e.g. Unix utilities EvolutionFromExisting
- 21. 21 What did ESBs do?
- 22. 22 • Monitor and control routing of message exchange between services • Resolve contention between communicating service components • Control deployment and versioning of services • Marshal use of redundant services • Cater for commodity services like • event handling, • data transformation and mapping, • message and event queuing and sequencing, • security or exception handling, • protocol conversion and • enforcing proper quality of communication service
- 24. 24 ”Monitor and control routing of message exchange between services”
- 25. 25 • Not really anymore. • “Services do one thing well” • Bunch of different approaches to service design and interaction. • No centralized point of “control”
- 26. 26 Aggregator Pattern w or w/o Proxy Chained Pattern Branch Pattern …..
- 27. 27 ”Resolve contention between communicating service components”
- 28. 28 “Smart endpoints and dumb pipes” - Martin Fowler http://martinfowler.com/articles/microservices.html
- 29. 29 “Control deployment and versioning of services”
- 30. 30 - Deployment - Configuration - Profiles / App Packaging - Service Discovery - Versions - Monitoring - Governance
- 31. 31 “Marshal use of redundant services”
- 32. 32 “Decentralized Governance” - Martin Fowler http://martinfowler.com/articles/microservices.html#DecentralizedGovernanc e
- 33. 33 “Cater for commodity services”
- 34. 34 • a lightweight service runtime • Cross – Service Security • Transaction Management • Service Scaling • Load Balancing • Deployment • Configuration • Profiles / App Packaging • Service Discovery • Versions • Monitoring • Governance • Failure Handling • Asynchronous vs. Synchronous • Cross – Service Logging • ...
- 35. 35 An approach.
- 37. 37 The Pieces
- 40. 40
- 41. 41
- 42. 42 • Implemented with Docker and Kubernetes • Use any JVM (or any technology) • Docker images, encourage static, well- defined, well-tested deployments • Provides networking, JVM isolation, orchestration, auto-scaling, health checks, cloud deployments • Still in community! • Supports OpenShift v3 Fabric8 V2
- 43. 43 And keep in mind….
- 44. 44 Operations and development are skills, not roles. Delivery teams are composed of people with all the necessary skills. �� Delivery teams run software products - not projects - that run from inception to retirement DevOps .. Is a culture.
- 45. 45 Let’s take one step at a time and not solve everything at once. aka “Evolutionary Design”
- 46. 46 Easy As That?
- 47. 47 • No silver bullet; distributed systems are *hard* • Dependency hell, custom shared libraries • Fragmented and inconsistent management • Team communication challenges • Health checking, monitoring, liveness • Over architecting, performance concerns, things spiraling out of control fast WARNING: Challenges ahead!
- 48. 48 Complex Runtime: many moving parts Distributed Systems are inherently complex Services are deployed on multiple instances Decentralized Data (Distributed Transactions vs eventual consistency) Communication between services (Network and Configuration) Synchronous vs. Asynchronous vs. Messaging Communication Communication overhead (n2n) Failure Handling (Circuit Breaker) Service-/Metadata Registry WARNING: Challenges ahead!
- 49. 49 ? Load Balancing API Management Configuration Deployment Monitoring SecurityGovernance Nodes Cartridges Versions Patches Changes
- 50. 50 And this is only the beginning... The industry is still learning a lot.
- 51. 51
- 52. 52 Correct functional decomposition is crucial for microservices: • pretty hard to get right from the start • a modular system can evolve to microservices • balance the needs with the costs • work on it evolutionary Takeaway:
- 53. 53 Are they here to stay?
- 54. 54 Nobody knows.
- 55. 55 Take with you today:
- 56. 56 • There is no single successor to ESBs. • The whole turned into pieces. • We’re still evolving them.
- 59. 59