Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Microservices, Boounded Contexts, and Everything in Between

Microservices, Boounded Contexts, and Everything in Between

Vladik Khononov

September 10, 2020
Tweet

More Decks by Vladik Khononov

Other Decks in Programming

Transcript

  1. vladikk doit-intl.com ”95% of the words are spent extolling the

    benefits of “modularity” and that little, if anything, is said about how to achieve it” Glenford J. Myers
  2. vladikk doit-intl.com ”95% of the words are spent extolling the

    benefits of “modularity” and that little, if anything, is said about how to achieve it” Glenford J. Myers
  3. vladikk doit-intl.com MarkeCng Sales Lead Lead Funnel Campaign Placement Landing

    Page Agency Insertion Order Message Campaign Proposition Desk Conversion Contact CDR Bounded Contexts
  4. vladikk doit-intl.com MarkeCng Sales Commissions Desks Sales Optimization CRM Telephony

    Creative Catalog Contracts Billing Campaign Management Identity & Access Ads Optimization Identity & Access
  5. vladikk doit-intl.com Business Domain: Customer Acquisi)on Bounded Context: Marke)ng Bounded

    Context: Sales Subdomain: Crea)ve Catalog Subdomain: Campaigns Mngmt Subdomain: Ads Op)miza)on Subdomain: Contracts Mngmt Subdomain: CRM Subdomain: Sales Op)miza)on Subdomain: Commissions Subdomain: Desks Mngmt
  6. vladikk doit-intl.com DecomposiCon Strategy #2: Subomains Campaign Management Service Content

    Catalog Service Desks Management Service CRM Service Users Service Billing Service
  7. vladikk doit-intl.com MarkeCng Creative Catalog Contracts Billing Campaign Management Identity

    & Access Optimization Campaign Management Campaign Placement Funnel Banner Landing Page Website Zone Asset Publisher Target Market
  8. vladikk doit-intl.com MarkeCng Creative Catalog Contracts Billing Campaign Management Identity

    & Access Optimization Campaign Management Campaign Placement Funnel Banner Landing Page Website Zone Asset Publisher Target Market Campaign Website Placement Funnel Bounded Contexts? Subdomains? EnCCes?
  9. vladikk doit-intl.com MarkeCng Sales Lead Lead Funnel Campaign Placement Landing

    Page Agency Insertion Order Message Campaign Proposition Desk Conversion Contact CDR
  10. vladikk doit-intl.com MarkeCng Sales Commissions Desks Optimization CRM Telephony Creative

    Catalog Contracts Billing Campaign Management Identity & Access Optimization Identity & Access Lead Lead
  11. vladikk doit-intl.com MarkeCng Creative Catalog Campaign Management Optimization Lead Sales

    Commissions Optimization CRM Lead Desks Telephony Support Contracts Billing Identity & Access
  12. vladikk doit-intl.com Bounded Context Consistency boundary of the language /

    model Define the biggest valid monoliths Required decomposition boundary
  13. vladikk doit-intl.com Campaign Management Campaign Placement Funnel Banner Landing Page

    Website Zone Asset Publisher Target Market Campaign Website Placement Funnel MarkeCng Creative Catalog Contracts Billing Campaign Management Identity & Access Optimization Bounded Contexts? No Subdomains? EnCCes?
  14. vladikk doit-intl.com “A service is a unit of functionality exposed

    to the world” - Juval Lowy “A mechanism to enable access to one or more capabilities, where the access is provided using a prescribed interface” - OASIS Service
  15. vladikk doit-intl.com Microservice = Microinterface Reducing coupling between services Limits

    reasons for change Easier to understand Better fault isolation More autonomy between services
  16. vladikk doit-intl.com Microservice = Microinterface Reducing coupling between services Limits

    reasons for change Easier to understand Better fault isolation More autonomy between services
  17. vladikk doit-intl.com Microservice & Databases Microservices should own its database

    No external access Access through Microservice’s API only Database = infinite interface!
  18. vladikk doit-intl.com The threshold upon which a system can be

    decomposed into microservices is defined by the use cases of the system that the microservices are a part of.
  19. vladikk doit-intl.com Campaign Management Campaign Placement Funnel Banner Landing Page

    Website Zone Asset Publisher Target Market Campaign Website Placement Funnel Subdomains? EnCCes?
  20. vladikk doit-intl.com ”Global complexity … the complexity of the overall

    structure of a program or system. I.e., the degree of association or interdependence among the major pieces of a program” Glenford J. Myers
  21. vladikk doit-intl.com ”Global complexity … the complexity of the overall

    structure of a program or system. I.e., the degree of association or interdependence among the major pieces of a program” Glenford J. Myers Composite / Structured Design, 1978
  22. vladikk doit-intl.com When you design a system…, then if the

    features can be broken into … loosely bound groups of rela>vely closely bound features, then that division is a good thing to be made a part of the design. This is just good engineering. Tim Berners-Lee Principles of design, 1998
  23. vladikk doit-intl.com Its is not only necessary to make sure

    your own system is designed to be made of modular parts. It is also necessary to realize that your own system … should always be designed to be a part of another larger system. Tim Berners-Lee Principles of design, 1998
  24. vladikk doit-intl.com A major part of this paper will be

    concerned with the ques>on of how good modularity can be achieved, that is, how modules can be chosen so as to minimize the connec5ons between them. Barbara Liskov A design methodology for reliable soIware systems, 1972
  25. vladikk doit-intl.com A microservice is a service with a micro

    interface. The threshold upon which a system can be decomposed into microservices is defined by the use cases of the system that the microservices are a part of.
  26. vladikk doit-intl.com A microservice is a service with a micro

    interface. The threshold upon which the system can be decomposed is defined by the use cases of the system that the microservices are a part of. …how to evaluate?
  27. vladikk doit-intl.com HeurisCc #1: Decompose to Bounded Contexts Do not

    implement conflicting models in the same service. Always decompose to Bounded Contexts.
  28. vladikk doit-intl.com HeurisCc #2: Don’t First Law of Distributed Object

    Design: “Don’t distribute your objects” MarCn Fowler
  29. vladikk doit-intl.com MarkeCng Sales Commissions Desks Optimization CRM Telephony Creative

    Catalog Contracts Billing Campaign Management Identity & Access Optimization Identity & Access Generic
  30. vladikk doit-intl.com MarkeCng Sales Commissions Desks Sales Optimization CRM Telephony

    Creative Catalog Contracts Billing Campaign Management Identity & Access Ad Optimization Identity & Access Generic Core
  31. vladikk doit-intl.com HeurisCc #4: Core Subdomains - Don’t Rush Adhere

    to subdomain’s boundaries. Decompose further only when you acquire domain knowledge.
  32. vladikk doit-intl.com SupporCng Subdomains No competitive advantage Support the Core

    Subdomains Can’t be bought / adopted Simple business logic
  33. vladikk doit-intl.com MarkeCng Sales Commissions Desks Sales Optimization CRM Telephony

    Creative Catalog Contracts Billing Campaign Management Identity & Access Ad Optimization Identity & Access Generic Core Supporting
  34. vladikk doit-intl.com SupporCng Subdomains No competitive advantage Support the Core

    Subdomains Can’t be bought / adopted Simple business logic
  35. vladikk doit-intl.com HeurisCc #5: SupporCng Subdomains - Safe Safe to

    decompose beyond the subdomain’s boundaries.
  36. vladikk doit-intl.com HeurisCc #6: Evaluate Consistency Requirements Read last write?

    - Two services, synchronous communication Service A Method A Service B Method B Sync call
  37. vladikk doit-intl.com HeurisCc #6: Evaluate Consistency Requirements Eventual consistency? -

    Two services, asynchronous communication Service A Method A Service B Method B Asynchronous Communication
  38. vladikk doit-intl.com HeurisCc #6: Evaluate Consistency Requirements Concurrency control? -

    Same service Read last write? - Two services, sync communication Eventual consistency? - Two services, async communication
  39. vladikk doit-intl.com HeurisCc #7: Public / Private Events Service Event

    Type 1 Event Type 2 Event Type 3 Event Type 4 Event Type 5 Event Type 6 Event Type 1000 …
  40. vladikk doit-intl.com HeurisCc #7: Public / Private Events Service Event

    Type 1 Event Type 2 Event Type 3 Event Type 4 Event Type 5 Event Type 6 Private event types (Implementation details) } Event Type 1000 …
  41. vladikk doit-intl.com HeurisCc #7: Public / Private Events Service Event

    Type 1 Event Type 2 Event Type 3 Event Type 4 Event Type 5 Event Type 6 Event Type 1000 … Private event types (Implementation details) }Public event types (Public interface) }
  42. vladikk doit-intl.com Service EmailChanged PhoneNumberChanged AddressChanged ContactDetailsChanged Private event types

    (Implementation details) } Public event type (Public interface) } HeurisCc #7: Public / Private Events
  43. vladikk doit-intl.com Same reasons for change? Same rate of change?

    Can be decoupled? Should be the same service? HeurisCc #9: Evaluate Reasons for Change
  44. vladikk doit-intl.com 1. A service is a unit of func)onality

    exposed to the world through its public interface. 2. A microservice is a service with micro interface 3. The “micro-interface” is rela)ve to the use cases of the system that the service is a part of
  45. vladikk doit-intl.com Heuris)c #1: Always decompose to Bounded Contexts Heuris)c

    #2: Don’t go further, unless you have to Heuris)c #3: Buy/adopt generic subdomains Heuris)c #4: Core subdomains - don’t rush Heuris)c #5: Suppor)ng subdomains can be decomposed early
  46. vladikk doit-intl.com Heuris)c #6: Evaluate Consistency Requirements Heuris)c #7: Private

    / Public Events Heuris)c #8: Explicitly Define Events Heuris)c #9: Evaluate Reasons for Change Heuris)c #10: Evaluate Services’ “Doors”
  47. vladikk doit-intl.com Bibliography 1. A Design Methodology for Reliable Soeware

    Systems, Barbara Liskov 2. Designing Autonomous Teams and Services, Nick Tune & Scoh Millet 3. Composite/Structured Design, Glenford Myers 4. Domain-Driven Design: Tackling Complexity in the Heart of Soeware, Eric Evans 5. Emerging Boundaries, Mathias Veraes 6. Implemen)ng Domain-Driven Design, Vaughn Vernon 7. Enterprise Integra)on Paherns, Gregory Hohpe, at al 8. Long Sad Story of Microservices, Greg Young 9. Managing Data in Microservices, Randy Shoup 10. Microservices, At Last Some Boundaries, Eric Evans 11. On the Criteria to be Used in Decomposing Systems Into Modules, David Parnas 12. Paherns of Enterprise Applica)on Architecture, Mar)n Fowler, at al 13. Principles of Design, Tim Berners-Lee 14. Programming WCF Services, Juval Lowy 15. What Every Programmer Should Know About Object Oriented Design, Melir Page-Jones