Industry Myth Busting
summary
Argues that choices must match goals and constraints, citing an integration platform built as 30 microservices on Spring Boot with one team and a real peak of one million users at the lottery draw, which benefits from scaling and isolated failures. Notes CI/CD and Kubernetes are now mainstream, explains Git/ClearCase history and how GitHub popularized cheap branching, critiques rigid GitFlow and absolutist trunk-based rules, recommends pragmatic tradeoffs on feature branches, tests (testcontainers, Micronaut), and realistic release cadences.
AI-written summary · about
chapters (9)
- 0:00Intro
- 1:241999
- 4:192013
- 10:41What are your goals?
- 17:16Feature branches vs trunk-based development
- 23:43Trunk-based development
- 33:05Developer testing
- 42:14Unit test vs integration test
- 45:19Outro
related talks
33mSoftware development practices for companies that want to make an impact
48mHow (not) to build a startup?
49mCase study of a good enough architecture
01h 03mBeyond the innovator’s dilemma
26mFeatures Versus Futures
27mThe curious case of the DevOps engineer and other things ...
27mArchitect CI/CD on Enterprise level
40mContinuous Delivery Anti-Patterns