Why Cross-Functional Teams Build Better Microservices
summary
Company reorganizes around three capability-aligned cross-functional teams using an inverse Conway maneuver to peel features out of the legacy jigsaw monolith. Small wins include a “hierarchy” service replaced by a JSON-on-S3 microservice behind API Gateway. Problems surface: inconsistent auth schemes, duplicated ELK stacks and wasted developer time, and a microservice with 1,000 commits showing only four infra changes. Solution: a Fabric team offering platform APIs (AWS, Let’s Encrypt) and a maturity path from custom to commodity.
AI-written summary · about
chapters (26)
- 0:00Intro
- 1:12Peters background
- 1:53Cobblers children
- 2:55Stovepipe Enterprise
- 4:10Mic Drop Development
- 5:38Team Structure
- 6:30Architecture
- 7:22Conways Law
- 7:52Fairmonts Law
- 8:25Conways Principle
- 9:28CrossFunctional Teams
- 10:25Responsibility
- 11:46The Microservices Book
- 12:25Inverse Conway Maneuver
- 14:30Jigsaw
- 17:46microservices help
- 19:27new problems
- 21:29food waste
- 23:28specialisms
- 24:53Infrastructure
- 32:59Photography
- 34:43AWS
- 36:12Fabric Tech
- 37:34Lets Encrypt
- 39:44Genesis
- 42:33autonomy and standardization
related talks
52mMicroservices & the Inverse Conway Maneuvre
38mMicroservices Architecture’s Influence on Team Organization
09mDon’t Forget Conway’s Law
58mMicroservices and the Inverse Conway Manoeuvre
01h 00mMicroservices and the Inverse Conway Manoeuvre
44mMicroservices - How to create problems by solving problems?
35mSeven years with microservices: a critical review
01h 01mMicroservices Gone Wrong