Software is a meal best served with different architectural spices
summary
Compares layered, hexagonal, SOA/microservices and event‑driven patterns and argues the goal is High cohesion and low coupling; recommends ports/adapters, dependency inversion, and isolated domain cores, and prescribes concrete tools: polyglot persistence, OAuth2, backend‑for‑frontend, CQRS + event sourcing, sagas, outbox pattern, RabbitMQ/Kafka. Claims microservices buy scalability but force distributed logs, versioning, network/DNS/startup sync, security and transaction complexity and often require circuit breakers and careful orchestration.
AI-written summary · about
chapters (13)
- 0:00🚀 Introduction: Software as a Meal
- 2:00The Ivory Tower: A Software Architect's Journey
- 4:00Layered Architecture: The Granddaddy of Software Styles
- 7:00Inverted Dependency Peaks: The Power of Abstractions
- 10:00Hexagonal City: Ports and Adapters for Integration
- 13:00Onions and Clean Architecture: Separating Core Logic from Integration
- 16:00Service-Oriented Emirates: SOA for Remote Components
- 20:00Microservices in the Holy Land: Scalability and Flexibility
- 24:00Event-Driven Architecture: Decoupling Producers and Subscribers
- 28:00Trade-offs of Microservices and Event-Driven Design
- 32:00Choosing the Right Architectural Pattern Based on Context
- 35:00The Importance of Personal Values in Architecture Decisions
- 38:00Final Thoughts: Architecture as a Set of Spices for Your Software
related talks
52mMeta modern Software Architecture
36mApplication Architecture Patterns
48mMeta Modern Software Architecture
54mArchitecture Foundations: Styles & Patterns (2021)
33mFrom Enterprise Architecture to Software Design - Critical Thinking
55mArchitectural Patterns for Rapid, Reliable, Frequent and Sustainable Development
01h 01mArchitectural Principles and Practices to Build MicroServices
56mDesigning in the World of Microservices