A Practical Use Case of Software Architecture Evolution
summary
A concrete e‑commerce MVP starts as a layered monolith in Java, evolves to a hexagonal ports-and-adapters model to decouple many third‑party integrations, then splits into independently deployable services with a Back‑end‑for‑Front‑End for client orchestration. Kafka handles high throughput with schemas generated into Java classes by a Kafka + Avro + Maven plugin, reducing lost orders under peak (Black Friday) load. Cost pressure drives selective AWS Lambda cost optimization for infrequent tasks (15‑minute, ~10 GB limits). Code and examples sit on GitHub.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:08Business drives architecture
- 2:34Layered MVP e-commerce
- 10:42Adding notifications
- 13:09Hexagonal architecture
- 22:05Microservices adoption
- 26:49Back-end for front-end
- 33:14Event-driven scalability
- 43:38Serverless cost optimization
- 48:58Combining architectures
related talks
51mCompetitive retail architecture with microservices
33mFrom Enterprise Architecture to Software Design - Critical Thinking
01h 13mRefactoring to a System of Systems
15mArchitecting Scalable Order Management Systems with Microservices
54mArchitecture Foundations: Styles & Patterns (2021)
51mMicroProcess Architectures: Planning for Change, & Retaining Flexibility
47mPorts, Adapters, and Other Ways to Stop Breaking Your Business Logic
01h 05mE-Commerce vs. Architecture!