Tinkertoys, microservices, and feature management...
summary
Claims: use feature flags to make containers stable and presentation dynamic, and to flip features on/off for cheap experiments; test channels and user flows by running with everything on and everything off; prefer test in production over costly staging — one client cuts about $10,000 a month by killing staging; demos include simulating partial outages, measuring end-to-end message time, and using Haggar swagger for API integration, with failures described and fixed in place.
AI-written summary · about
chapters (17)
- 0:00Intro
- 0:15Tinkertoys, Microservices, and Feature Management How to build for the future
- 2:55The state of the now
- 4:00The future is fractal
- 4:36Why do we test?
- 5:05What do we test for?
- 5:319s don't matter if the user is unhappy.
- 11:19The beautiful future
- 14:13Modular (microservices)
- 15:15A distinctive method of developing software systems that tries to focus on building single-function modules with well-defined interfaces and operations.
- 15:57Semantics Syntax
- 17:33Testing experience, not embodiment
- 18:40Why microservices are like Tinkertoys
- 22:23Combinatoric Testing Complexity
- 24:12Do all the things in production
- 25:14This is a roadmap It may not be your roadmap
- 26:50Recording and Production Confreaks
related talks
53mTinkertoys, microservices, and feature management: How to build for the future
27mTinkertoys, Microservices, and Feature Management: How to Build for the Future
35mFeature Toggles, Trunk-Based Development and Continuous Delivery
05m5 Life Hacks Using Feature Management
05mFeature Flags
32mMaster your software delivery with feature flags
50mThe Story of One Feature Flag
07mLightning Talk: Developer's Toolbox for Testing in Production