Shattering your application into an umbrella project
summary
Shows how a Phoenix 1.2 monolith becomes an umbrella project by splitting into OTP apps for interpreter, RPC, Lighthouse, partner, SSH tunnel and web, using RabbitMQ, Ecto and an Ember frontend. Describes building a transport‑neutral resource layer (the calcinator package), an RPC supervisor that owns RabbitMQ connections (interpreter RPC), and an SSH tunneling Observer workflow that actually works. Reports faster builds and extractable Hex packages (almic, calcinator) but warns about Docker path quirks and a test race with repo startup.
AI-written summary · about
chapters (8)
- 0:00Start
- 9:19Owner Error Ownership
- 12:36Interpreter Server Observer
- 19:47Pros and Cons
- 21:59Json Api Format Validation
- 22:52Rpc Servers
- 26:19Support for Sandbox Access
- 30:53Separate Your Ui into Different Otp Apps
related talks
34mFrom Front End to Full Stack with Elixir and Phoenix
32mFrom Monolith to Micro Frontend
40mMonoliths Between Microservices
22mBreak Up With Your Frontend Monolith
12mLiberating your Application from Framework Tyranny
44mDefy Architectural Uncertainty by Building Schrödinger's App
58mFrom Zero to Live with Functional JavaScript Applications (Part 2)
51mFrontend Monoliths: Run if you can!