Booking.com tech modernisation
summary
Booking.com replaces a monolithic Perl codebase with a service-oriented stack built on Java GraphQL React, backing data in Cassandra Spring Boot Kubernetes and federating APIs via Apollo while front ends run Preact/TypeScript, SwiftUI and Jetpack Compose. The property page breaks into 140 unique UI components and after multi‑year work about 2/3 of the property page is modernized; ownership and cross‑platform parity improve, velocity shows mixed gains and incremental rollout plus A/B testing proves safe.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 0:54Tech modernization journey
- 3:06Perl challenges in hypergrowth
- 6:18Modernization goals
- 7:22Team responsibilities
- 8:04Target architecture steps
- 9:51Avoiding Ivory Tower trap
- 10:34Off-the-shelf solutions
- 11:15Top-down bottom-up approach
- 13:00People-first change management
- 16:10Rewards alignment
- 17:14Breaking work into components
- 20:03Technical architecture overview
- 22:11Controversial completion calls
- 23:35Program management
- 23:57Team ownership
- 26:09Running dual stacks
- 28:15Teamwork beyond engineering
- 30:20Strategic product prioritization
- 31:25Results and outcomes
- 32:26Key takeaways
related talks
23mBuilding the Graph at Booking.com
23mBuilding the Graph at Booking.com
23mOur Journey To a Unified Developer Experience With Backstage
25mMulti-platform design system at Booking.com
25mThe Lego Approach: Leveraging Reusability for a Seamless...
29mUsing server-driven UI to rapidly iterate across platforms
30mChanging the world of travel with Angular and measuring...
38mMigrating from PHP legacy code to React & Best Practices in React