Skip to content
0:00 / 0:00

#phoenix#elixir#domain-drivendesign

ElixirDaze 2018 - Building beautiful systems with Phoenix contexts... by Andrew Hao

Confreaks

42K subscribers • 85 videos on Hallway • Conference channel

YouTube
  • Recommended by 2 people: 2 in engineering communities.
  • Presented by Andrew Hao
  • May be out of date. Uploaded 8 years ago, in an area where tools change fast.

Intermediate. Assumes working knowledge.

23K views8 years ago2 recommendations

Software designWeb developmentDomain-driven designSoftware architectureElixir and Erlang

Andrew Hao explains how to design clean, maintainable Phoenix applications using contexts and Domain-Driven Design principles.

ElixirDaze 2018 - Building beautiful systems with Phoenix contexts and Domain-Driven Design by Andrew Hao

Why it's here

2 people recommend this

What people say. Recommended for engineers looking to understand how to apply Domain-Driven Design principles to Phoenix contexts.

u/nlayeredhumanin r/elixir • Recommends

On “Did contexts kill Phoenix?”

Coming from a heavy DDD background myself I think there is a lot of things that can be improved. First time I used phx.gen.auth I was shocked that the recommended context name was Accounts since that clashes in almost any finance application. I've found that Identity works much better as it accurately represents authentication/authorization concerns without conflicting with domain concepts. I think Andrew does a really great job of explaining contexts clearly in this talk link to this video I understand that while the name context is used maybe it was never meant to be a reference to DDD? Naming contexts and naming in general is really one of the hardest parts of any development endeavor.

u/foucistin r/elixir • Recommends

On “Question about Phoenix and using resources across contexts”

contexts are an idea that come from DDD (domain-driven design) so it might be helpful to look at some DDD stuff in phoenix world.. this youtube video might be helpful link to this video