E-Commerce vs. Architecture!
summary
Argues that architecture should minimize implementation overhead (“exzellente complexity”) and foster shared mental models rather than following fashion. Gives concrete failure patterns—e.g., splitting a PHP monolith into 30 components across 7 languages with 6 developers slowed delivery, and microservices without automation fail when infrastructure and feedback loops are missing. Compares choices (off‑the‑shelf platforms like Magento/Hybris, modular monoliths, serverless/AWS) and recommends picking the approach that keeps overall complexity visible and keeps the right people together.
AI-written summary · about
chapters (4)
- 0:00Introduction
- 20:40E-Commerce architecture challenges
- 46:50Essential vs excellent complexity
- 1:03:14Summary
related talks
50mThe Unbearable Weight of Architecture
44mDeliberate Architecture
01h 00mAgile Architecture
43mMonolith? Microservices? Who cares?
45mThe Unbearable Weight of Architecture
33mFrom Enterprise Architecture to Software Design - Critical Thinking
39mMinimal Viable Architecture
27m“Good Enough” Architecture Part 2