Your monolith, Elixir and you
summary
Company builds two separate Elixir apps to augment a Rails monolith: a courier tracking service and a fulfillment UI. Tracking uses Elixir/Phoenix sockets then falls back to a REST endpoint for Android, authenticates couriers with JWT auth, stores geo points in Postgres with GIS, and handles many more concurrent clients (speaker contrasts ~100 in Rails to 2M vs 100 clients). Tracking deploys quickly and works well; fulfillment faces library, testing and adoption delays.
AI-written summary · about
chapters (7)
- 0:00Start
- 7:52Replace it step by step
- 13:37Spark of Enthusiasm
- 18:19Header Payload Signature
- 31:12Be careful with new technologies!
- 31:57Macroapplications
- 36:08KNOW THE RULES
related talks
34ms/15 years old TCP Service/Elixir HTTP Microservice/g
40mBreaking the Monolith! Decoupling a Legacy Monolithic Application
46mFrom Monolithic Monster to Majestic Microservice App
32mQuietly Strangling the Monolith - a real-world migration of a high traffic monolith
02h 29mPractical advice for building glorious monoliths
30mTackling Technical Debt at Adobe: A Story
33mFireside chat - Monoliths, Microservices & Modernization – Practical Strategies
24mModernise your monolith using strangler pattern