s/15 years old TCP Service/Elixir HTTP Microservice/g

on YouTube ↗34m

" summary

Replaces a 15‑year‑old C TCP service with an Elixir HTTP+JSON microservice that handles ~15 million ad insertions per month, preserves the monolith database as the integration point, and keeps the existing external contract so clients never change. Engineers map the old positional payload (32 parameters) into new logic, move over heavy business rules (one function had ~400 lines), collect metrics to compare purple/green traffic, and achieve a zero-downtime rollout while eliminating daily memory‑leak restarts.

AI-written summary · about

" chapters (13)

1. 0:00Introduction and speaker
2. 2:58Maracanã stadium analogy
3. 5:05Software rewrites debate
4. 8:00Software rot and pragmatism
5. 10:22OiAxad marketplace background
6. 13:01Problems with legacy TCP service
7. 17:26Decision to rewrite from scratch
8. 18:11Strategy for zero-downtime replacement
9. 20:26Architecture comparison
10. 23:00Metrics and data integrity
11. 28:20Key takeaways and strategy
12. 30:31When to rebuild software
13. 32:20Final advice and Q&A

" related talks

• 37mFrom the ground to the starsBruno Ripa · ElixirConf EU Virtual 2020
• 41mYour monolith, Elixir and youTobias Pfeiffer · Code BEAM Lite Berlin 2018
• 45mElixir and the Internet of ThingsDoug Rohrer · Strange Loop 2014
• 48mExtracting a microservice from a 15-year-old monolith: a one-year adventureStanislav Kondratev · HighLoad++ 2024
• 45mRewriting Critical Software in Elixir - A Case StudyRenan Ranelli · QCon São Paulo 2019
• 38mElixir Adoption at Scale: A Comprehensive GuideBen Marx · Lonestar ElixirConf 2017
• 47mElixir for curing product development painsMichael Krax · Code Elixir LDN 2018
• 45mElixir: une potion pour mixer complexité et concurrence en temps réelMaxime JANVIER · Devoxx France 2023