Using Your Umbrella
summary
Claim: umbrella repos let teams compose clear bounded contexts as independent Elixir applications. Concrete patterns: a single DB app that owns migrations and the Ecto repo, Phoenix as a thin web layer, and keeping schemas duplicated per context when fields differ. Tooling used: mix tests run from the top level, generators in Phoenix 1.3, docs with ExDoc, and packaging with Distillery releases. Gotchas: no circular app deps, run migrations inside each app, and dependency overrides sometimes become necessary.
AI-written summary · about
chapters (7)
related talks
30mPhoenix Is Not Your Application
47mGood behaviour: Cultivating Healthy Elixir Teams & Codebases
59mKeynote: Elixir Should Take Over the World
40mKeynote: The Pendulum
39mKeeping Code Consistent
06mResilient Code, Resilient Engineer: Lessons from Changing Requirements
33mHigh availability with Elixir and Erlang
45mKeynote: One Monolith, Many Teams: Growing an Org...