Self Contained Systems: The Good, the Bad & the Ugly
summary
Self Contained Systems (SCS) macro-architecture used in large e‑commerce platforms is examined, focusing on its technical benefits like shared‑nothing and loose coupling that enable independent vertical development and scalability. The talk analyzes where complexity is relocated—into domain slicing, splitting naturally related topics, and increased process overhead—and discusses the consequences for development processes, team organization, critical decisions, common pitfalls, and where to be particularly careful.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:09From monoliths to SCS
- 6:58Vertical scaling
- 10:38Big requirements
- 13:45Team communication
- 17:36Domain assignment
- 23:12Ownership in teams
- 27:28Horizontal integration
- 31:03SCS pros and cons
- 37:24Q&A
related talks
47mSay Goodbye to Microservices, Say Hello to Self-Contained Systems
43mGoodbye Microservices, Hello Self-Contained Systems
01h 05mE-Commerce vs. Architecture!
27m“Good Enough” Architecture Part 2
44mHow to test self-contained Systems
45mE-commerce platform. Core build principles, problems and guidelines.
45mAdaptive Socio-Technical Systems
33mFrom Enterprise Architecture to Software Design - Critical Thinking