Building beautiful systems with Phoenix contexts...
summary
A concrete playbook emerges: Phoenix contexts encapsulate persistence and domain logic and expose a small public API, use Ecto schemas and nested aggregates as the aggregate root, and map business vocab into code via a context map and ubiquitous language exercise. Practical patterns include struct conversion and collaborating schemas to avoid a god user, an anti‑corruption layer for cross‑context translation, and publishing domain events (example: eventbus) to decouple side effects while passing the full aggregate route.
AI-written summary · about
chapters (5)
- 0:00Start
- 3:26Modularization
- 8:00How do we design system boundaries?
- 22:03Concept sharing Or: Double Trouble
- 35:03In conclusion
related talks
36mBuilding Beautiful Systems with ...
40mController Control: Designing Domains for Web Applications
34mFrom Front End to Full Stack with Elixir and Phoenix
37mBuilt to last: A domain-driven approach to beautiful systems
01h 02mBuilding that glorious monolith. And carving it too.
32mShattering your application into an umbrella project
35mBuild Complex Domains in Rails
58mBuilding that glorious monolith. And carving it too.