BlaBlaConf 2021 Day 3: Security and Architecture
summary
Explains when microservices help and when they hurt with concrete tradeoffs: use Saga pattern or two‑phase commit for distributed transactions, prefer local database per service, and rely on a message broker plus compensating actions for order/booking workflows; cites Amazon running 100+ microservices and shows how failures propagate, caching and service discovery choices, and why splitting wrong causes outages. Includes a live microservice demo that flails under time limits so take the architectural warnings as actionable.
AI-written summary · about
chapters (11)
- 0:00Intro
- 8:50Opening panel
- 29:03A Walkthrough Keycloak مقدمة ال with Zakaria Amine
- 1:09:16The right questions to ask when using microservices with Driss ALLAKI
- 1:42:10Building Microservices Architecture The Right Way based on Saga Pattern with Ali Ben Messaoud
- 2:10:00Binary Exploitation 101: Offensive C Security with Hammadi Agharass
- 2:56:44Break
- 3:16:39Software Quality Assurance Craftsmanship with Abdelghani Achibane
- 3:57:50Distributed systems 102 with Mehdi Chercher
- 4:33:26IT Event Planning 101 with Aicha Laafia
- 4:54:30Swerty Mulana
related talks
43mPanel: Microservices, Where Did It All Go Wrong
38mMicroservices, a bittersweet symphony
40mCAPtivating architecture: Navigating Distributed Systems and Microservices
54mThe Long Sad History of Microservices
59mGranularity & Communication for Microservice Architectures
58mImplementing Event-driven Microservices
57mSOA lessons learnt (OR Microservices done better)
49mChallenges in Implementing Microservices