Go Faster -Impact on Technology, Process and Organization
summary
Claims that speed requires concrete changes not buzzwords: move to cloud and containers, replace a central RDBMS with an event bus (Kafka), decentralize data into small tuned stores, and adopt the Netflix open stack and Docker. Evidence: a team of 53 does 652 deployments in one week, MailOnline replaces ~130,000 lines of Java with 4,000 lines of Clojure and serves 3.2 PB/month. The built systems run and enable rapid experimentation.
AI-written summary · about
chapters (26)
- 0:00Start
- 0:24Industry "Hot" Topics
- 1:37Why: New Problem Domains: The Cynefin Framework
- 5:53Why: Competition is coming
- 7:45How Fast Can You Go?
- 7:55Project Delivery Cycles
- 11:31Hardware Lead Times
- 14:11Services Impact
- 16:58Emerging: Event Bus
- 19:58New Architecture Patterns
- 21:36Incremental Applications
- 23:29Databases: Holy Grail or Ball-and-Chain?
- 27:51Open Source: Netflix
- 28:25Open Source: Docker
- 29:20Disruptive Technology: Functional Languages
- 31:12Mitigate Process Inhibitors
- 32:34New Vision of "What" to Build
- 34:23Re-think Interactions
- 36:17Measure What Matters
- 37:37Mitigate Organization Inhibitors
- 38:03Over-Specialization
- 38:46Specialization Institutionalized with Titles
- 39:24Solution: Fix the Titles
- 40:36New Titles for New Projects
- 43:22Non-dedicated Leadership
- 44:06Bring Work to the Team...
