Download as PDF, PPTX
Uploaded byEberhard Wolff
Beyond Microservices
The document discusses microservices architecture, highlighting its advantages such as independent development, scalability, and enhanced resilience, as well as the challenges like consistency and the complexity of large-scale refactoring. It emphasizes the need for a tailored architectural approach beyond traditional microservices, advocating for well-defined bounded contexts and the inverse Conway maneuver to improve self-organization and team autonomy. The author concludes that the architecture should be chosen based on project-specific trade-offs to maximize benefits and minimize drawbacks.
More Related Content
Beyond Microservices
- 1.
- 2.
- 3.
- 4.
- 5.
- 6.
- 7.
- 8.
- 9. Decoupling > Originally: Changing amodule does not influence other modules. > i.e. independent development
- 10. Microservice Decoupling > Independentscaling > Independent technical decisions > Decoupled crashes > Security: firewalls etc
- 11.
- 12.
- 13.
- 14.
- 15.
- 16.
- 17.
- 18.
- 19. Replaceability > Small componentshard to mess up > Each module can be replaced > …small green field project > ...different technology stack possible
- 20.
- 21.
- 22.
- 23.
- 24. Build Pipeline for Microservices >Build pipeline per Microservice > Smaller > Easier to set up > Less features (3rd party systems) > Faster Feedback: Less tests
- 25.
- 26.
- 27.
- 28.
- 29. Inverse Conway Maneuver >Architecture drives organization > Cross-functional team (database, logic, UI) > Team responsible for Bounded Context(s)
- 30. Take one hugeproject and make it several small projects…
- 31. Self-organization > With somuch independence… > ...teams can decide for themselves. > Self-organization
- 32.
- 33.
- 34.
- 35. Consistency Order Invoice Delivery Order #42 is cancelled! ✅ ✅ ⁉ Goodsmight be delivered if order arrives after cancellation.
- 36. This is quitecommon without microservices.
- 37.
- 38.
- 39.
- 40.
- 41.
- 42. Refactorings > Move codeto a new service: Easy > Move code from service to service > Might be a port to a different language > Hard
- 43. Global Refactorings > Reallyhard: Global restructuring > i.e. moving everything to a different place. > …but that is always hard… > ...and the result of a major screwup. > Do you want to optimize for this?
- 44. Many New Technologies >Microservices framework > Service discovery > Routing / API Gateway > Continuous Delivery pipeline > Docker > Docker scheduler (Kubernetes) > ....
- 45. Challenges Consistency Fail safeness Largescale refactoring New Technologies
- 46. Microservices are an allor nothing approach.
- 47. Microservices are an allor nothing approach.
- 48. Which benefits are important? Whichchallenges acceptable?
- 49.
- 50.
- 51.
- 52.
- 53.
- 54.
- 55.
- 56.
- 57.
- 58. Centralized Database is abad idea.
- 59.
- 60. Layered iOS Android Web OrderProduct Delivery InvoiceCustomer
- 61. Layered: Issues > Changinga business process cause many changes > …in Frontend and many backend > Lots of communication between teams and components
- 62.
- 63.
- 64.
- 65.
- 66.
- 67.
- 68. Order Shipping address Tracking # Items ItemCategories Priority shipping Customs # Account # ... Credit card # Order #
- 69. My Domain Modelis a mess!
- 70. Bounded Context > Domainmodel is only valid for one context > There is no universal data model! > See all failed SOA attempts
- 71. Order Shipping address Tracking # Items ItemCategories Priority shipping Customs # Account # ... Credit card # Order # Customs Order Recommen- dations Order Tracking Order Shipping address Tracking # Item Categories Priority shipping Customs # Payment Order Account # Credit card #
- 72. Self-contained Systems Search InvoiceLogisticsCheckout Web Web Web Web See http://scs-architecture.org
- 73.
- 74.
- 75.
- 76.
- 77.
- 78.
- 79. Build order / Architecture management Buildorder / Architecture management
- 80.
- 81.
- 82.
- 83.
- 84. Clean architecture with alot less technical challenges!
- 85.
- 86. Conclusion > Microservices area set of architecture decision > Architecture is about trade-offs > Architecture is different for each project > Go beyond microservices by picking the best decisions! > …and gain most benefits
- 87. Usually bad tradeoffs >Centralized database > Layered model
- 88. Usually good tradeoffs >SCS, Bounded Context, Microlith > Strongly separated modules