Microservices Day London | David O'Donoghue, Zalando
summary
Before micro-services teams have tight technical dependencies forcing simultaneous build test and release cycles and slowing delivery; after moving to micro-services each team owns, build test deploy support and releases its services independently so release cadence becomes independent and velocity increases. The engineering organisation reorganises around autonomous teams with greater freedom, and the microservices rollout at Zalando is presented as a working change that yields both technical advantages and measurable organisational autonomy.
AI-written summary · about
related talks
38mFrom Monolith to Microservices at Zalando
38mMicroservices Architecture’s Influence on Team Organization
49mMicroservices: An unexpected Journey
50mMicroservice specifics illustrated by an e‑commerce platform
45mMicroservices: A retrospective
44mIs It Time Already? Microservices Are Dead; Long Live Microservices!
26mMicroservices
50mChallenges in Implementing Microservices