Building Beautiful Systems with ...
summary
Argues that Phoenix contexts are concrete Elixir modules that group business logic and hide persistence (Ecto) and shows a hands‑on Context Mapping exercise that produces bounded contexts and a ubiquitous language. Demonstrates refactoring a messy controller into context calls, creating a collaborator schema to persist a mechanic, using EventBus publish/subscribe for decoupled side effects, and advises avoiding cross‑context joins and starting small so the architecture yields cohesive, loosely‑coupled systems.
AI-written summary · about
chapters (4)
related talks
39mBuilding beautiful systems with Phoenix contexts...
40mController Control: Designing Domains for Web Applications
37mBuilt to last: A domain-driven approach to beautiful systems
34mFrom Front End to Full Stack with Elixir and Phoenix
55mCharting the uncharted: Discovering and evolving bounded contexts
48mGrowing & Thriving in a Multi-model World
52mEvolving a Pragmatic, Clean Architecture A Craftsman's Guide
28mUnpopular Opinions