So What are Microservices
summary
Claims that microservices cut time to deploy and increase velocity with concrete tooling: service catalog that auto-indexes APIs, RDS and KMS on AWS for fast provisioning and PCI scoping, and sidecars/protobufs for cross-language IPC. Migration is iterative not a big rewrite; teams split domains, each service owns its own data and DB, and surprising costs include org churn (often 20–40% leave) and the need for tracing/circuit-breaker libraries everywhere to avoid cascading failures.
AI-written summary · about
chapters (5)
- 0:00Start
- 16:31How Would You Organize Teams around those Different Services
- 25:48Mismatch between the in Place Processes in Your Organization and the Micro Service Architectures
- 28:39How Much Autonomy Do To Do Developers Have in Choosing Technologies and Languages
- 42:05Is It Common To Have Your Micro Services Communicate with the Database Directly or
related talks
45mMicroservices: A retrospective
49mMicroservices: An unexpected Journey
25mMaking microservices a behaviour not a buzzword
48mChallenges in Implementing MicroServices
26mPros/Cons of Microservices
47mIt is not just Microservices
44mIs It Time Already? Microservices Are Dead; Long Live Microservices!
26mMicroservices
