Skip to main content

Architecture Patterns, Service Decomposition, DDD, Bounded Context and Database per Service

Learn Architecture Patterns, Service Decomposition, DDD, Bounded Context and Database per Service (Phase 1 · Microservices Fundamentals (Core), Microservices) with worked examples, diagrams and interview questions. Free on JavaSchoolLab.

Service decomposition • How to split a system: by business capability (catalogue, ordering, payment, shipping) or by subdomain (DDD). Not by technical layer (a "database service", a "UI service") and not too fine-grained (nano-services). • Good service boundaries: high cohesion (things that change together live together), loose coupling (few, stable interactions), single owning team , own data, can be explained in a sentence, can be deployed alone. Conway's law : system design mirrors communication structure: design teams and services together. • Strangler fig migrates a monolith step by step....

More lessons in Phase 1 · Microservices Fundamentals (Core)