Vertical Architecture and Distributed Development - How Breuninger Scales
summary
Breuninger argues that a vertical architecture—organizing teams by Customer Journey domains that each own their database and infrastructure—scales better than large horizontal monoliths tied to cross-cutting platforms (hybris/IBM/SAP). The implementation splits the shop into vertical products with a frontend proxy on top and independently deployed teams using pragmatic microservices, yielding faster time-to-market and easier distributed development; remaining challenges are macro constraints (Oracle, compliance) and poorly managed microservices.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 0:12VERTICAL ARCHITECTURE
- 4:40WARNING
- 7:30OUR VISION
- 10:22CONTEXT: BREUNINGER SHOP REDEVELOPMENT
- 12:36WHY? TIME TO MARKET
- 13:29GOALS OF PRODUCT DEVELOPMENT I
- 19:58HOW, VERTICAL?
- 21:23ORGANIZATION REDESIGN
- 27:12MACRO AND MICRO ARCHITECTURE
- 33:07WHY IS THIS FUN?
related talks
45mTowards Architecture Organization Topologies for Sustainable Fast Flow of Change
38mFrom Monolith to Microservices at Zalando
46mDigital scale-up architectural patterns
25mAgile architects: classical conductors or band member?
19mHarnessing Microfrontends: Platforms for Web Apps
54mDesigning for change with Vertical Slice Architecture
50mTowards an Evolutionary Architecture
58mDesigning for change with Vertical Slice Architecture