From a Ruby on Rails Monolith to Elixir and Elm Microservices
summary
MyMeds&Me migrates a working Ruby on Rails monolith into an event‑driven microservice platform using Elixir backend, Elm frontend and RabbitMQ for message brokering, trading JSON blobs in Postgres for graph‑style reports, websockets via Phoenix, container images and orchestration, and automated deploys. The team targets handling up to four products and ~20 customers (an extrapolated ~320 environments), ships a sales demo and aims for production by year end, and reports reduced coupling, easier real‑time analytics and fewer cross‑service regressions.
AI-written summary · about
chapters (9)
- 0:00Scaling challenges
- 2:42Compliance and requirements
- 3:16Monolith limitations
- 3:55Entropy and complexity
- 5:17Scaling strategy
- 9:05The Raven tactic
- 9:23Microservice architecture
- 23:03Communication and data
- 25:30Elixir and Elm integration
related talks
40mMonoliths Between Microservices
39mTaming Monoliths Without Microservices
28mBringing Your Rails Monolith Along As The Business Grows
51mMicroservices and Microfrontends: Scaling, Learning, Growing
34mFrom Front End to Full Stack with Elixir and Phoenix
55mThat's My Monkey (...)
40mMigrating from a monolith to a new service
23mClient/Server Architecture: Past, Present, & Future