The hitchhiker's guide to software architecture and design
summary
Designs a Donut@Home e‑commerce platform by asserting specific choices: target SLOs of ~95% availability and ~2s page responses for most transactions, record decisions in ADR + C4 context diagrams, and run a risk matrix and POCs for sizing. Architecture settles on microservices with a Kafka event backbone to decouple shopping and billing, externalize payments (PCI DSS) and delivery, use Spring Boot and Quarkus services with Postgres/Mongo, and build observability by design rather than bolting it on.
AI-written summary · about
chapters (26)
- 0:00Intro
- 0:33Meet Alexandre and Raphal
- 1:16Wheres the end
- 1:33Donut at home
- 2:44First meeting
- 3:36Nonfunctional requirements
- 6:40Risk
- 9:41Architecture approach
- 10:21C4 model
- 11:27System context
- 12:06Design process
- 15:21Summary
- 16:51Architecture characteristics
- 19:05Architecture types
- 20:16Orchestration
- 21:24Events
- 22:00Microservices
- 25:39Architecture design
- 31:04Observability
- 31:48Voice analysis metrics
- 32:17Accept new point of views
- 33:42Make it real
- 33:57Private or public cloud
- 36:44Compliance with requirements
- 40:53Presentation
- 42:41Questions
related talks
33mFrom Enterprise Architecture to Software Design - Critical Thinking
45mE-commerce platform. Core build principles, problems and guidelines.
51mCompetitive retail architecture with microservices
50mA Practical Use Case of Software Architecture Evolution
36mApplication Architecture Patterns
42mSoftware Architecture in the Age of Agility and DevOps
27m“Good Enough” Architecture Part 2
46mArchitecture & DevOps