Tackling Technical Debt at Adobe: A Story
summary
Elixir monolith migrates background work to Oban Pro+Web and a Broadway pipeline, cuts API instances from 22 down to 9 while traffic doubles, and halves 99th‑percentile response times; Credo and Dialyzer find refactor targets, Sorcerer automates large-source edits, Mox removes S3 flakiness, and mixed_test speeds CI by 4x. Postgres upgrades and partitioning shrink a giant index from 1.5 TB to ~100 GB and eliminate costly bulk deletes, and these changes measurably improve stability, observability, and developer onboarding.
AI-written summary · about
chapters (9)
- 0:00Introduction and context
- 5:19Tooling and migration
- 8:08Code quality improvements
- 10:21Advanced refactoring tools
- 12:53Feature management
- 13:50Developer experience
- 17:52Observability and Postgres
- 20:53Database maintenance
- 24:46Future goals and Q&A
related talks
48mThe Journey of a strongly coupled Monolith into the Cloud Land
54mCtrl-Alt-Del: learning to love legacy code
23mDevOps and Legacy Code
18mPlatform-Oriented Legacy Modernization
28mAcceptable Upgrades
59mArchitecture Modernization Anti-Patterns: The Cost of Good Intentions
55mModernizing Legacy Code - While Not Bringing Down Prod
05mBalancing Technical Debt and Modernisation in DevOps