Building Umbrella Project
summary
An Acme Bank example implements double-entry accounting in a standalone ledger app, extracts money and authentication into separate OTP apps, and wires two Phoenix frontends (customer and back‑office) into one umbrella. The repo runs per-app tests, shares build/log paths, and starts Phoenix on ports 4000/4001; deployment uses a simple Heroku proxy and Distillery supports umbrella releases. The claim is that umbrella apps give many microservice benefits (clear boundaries, independent deploy/test) while keeping one repo and fast local iteration.
AI-written summary · about
chapters (12)
- 0:00Inspiration and concepts
- 4:08What is an umbrella project
- 6:52Building the bank core
- 10:55Accounting domain logic
- 14:37Persistence and use cases
- 17:09Creating shared components
- 18:51Building the web interface
- 20:50Admin panel and services
- 22:52Deployment and proxying
- 23:51Authentication subsystem
- 27:02Project demonstration
- 30:37Comparison and Q&A
related talks
42mUmbrella Apps-Winter is coming
15mMicroservices with Elixir
12mLiberating your Application from Framework Tyranny
57mHow I sliced your app
51mBuilding a multi-account, multi-runtime service-oriented architecture
41mBuilding a Bank (with DDD, Microservices, and Autonomous Teams)
40mFacing the Monolith Overcoming Monolithic Applications with SOA
44mRoute to microservices the epic voyage of a fintech leader