Doing the DDD dance with Google Cloud
summary
Claims that Domain‑Driven Design maps cleanly onto Google Cloud and shows concrete pairings: ubiquitous language, bounded contexts and context mapping paired with Cloud SQL, Firestore and Cloud Pub/Sub for events, Cloud Run as the general runtime and Cloud Spanner for planetary scale at higher cost. Advice includes separate datastores per service, ports-and-adapters for infra separation, version APIs, favor event-driven domain events for loose coupling, and consider a modular monolith to save cost; architecture is practical and implementable.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:00Google Cloud services
- 2:28Domain Driven Design
- 6:04Strategic DDD patterns
- 14:45Tactical DDD patterns
- 19:22DDD on Google Cloud
- 25:08DDD in Cloud architecture
- 26:14Final recommendations
related talks
56mMicroservices and Domain-Driven Design — The Strategic Parts
29mFrom Monolith to Cloud-Ready Microservice Architecture with DDD
49mDDD & Microservices: At Last, Some Boundaries!
01h 01mImplementing DDD Patterns with Spring
56mDDD in Microservices: Complexity versus Complexity
34mThe Road to a Distributed Application, or the Pitfalls of CQRS/DDD
45mUsing DDD To Decompose Your Monolith
40mMicroservices without DDD is risky business!