Balancing Speed and Reliability The Double-Edged Sword of Third-Party Libraries
summary
A Google Maps SDK server change on April 23, 2020 causes app crashes for days, prompting rollbacks and two hotfixes and requiring teams to delete three files to stop the failure; incident blocks millions of users, costs millions of dollars, consumes thousands of developer hours and hundreds of engineers over four days. Response creates formal library governance, chooses Coil but rejects Facebook Auth, permits Twilio and Ads via heavy mitigations, and builds an automated recovery system called Black Swan plus dynamic feature modules to contain and recover future failures.
AI-written summary · about
chapters (21)
- 0:00Introduction and speaker
- 1:17Google Maps SDK outage
- 5:29Third-party libraries overview
- 7:58Library governance explained
- 10:45Business priorities for libraries
- 13:53Library requirements checklist
- 15:41Handling exceptions in governance
- 16:43Library upgrades and greenkeeping
- 17:24Real-world governance examples
- 21:17Programmatic defense strategies
- 23:00Feature flags and testing
- 24:03Delayed initialization risks
- 25:26Startup crash vulnerabilities
- 27:14Play Services and dynamic behavior
- 28:17Dynamic feature loading
- 28:59Transitive dependency conflicts
- 31:07Library abstraction techniques
- 33:12Crash recovery systems
- 34:56Automated recovery actions
- 36:43Hotfixes and force upgrades
- 38:05Summary and Q&A
related talks
40mBalancing Speed and Reliability- The Double-Edged Sword of Third-Party Libraries
24mThe missing guide for deciding between 3rd party library and custom code -JSWORLD 2023
24mDrawing the line between 3rd party and custom code
42mYour library sucks, and why you should use it
45mThe Balance Between Speed and Reliability: Reuse vs Re-verify
38mBuilding libraries for the next 25 years
01h 17mDevelopment strategies: You've written a library - now what?
27mDrawing the line between 3rd party and handcrafted code