Wrapping Up: Optimize Your Application Design

Application design is a big topic, and we’ve just scratched the surface here. We hope you’ve gotten some ideas that will help inform the choices you make as your projects evolve.

We recommend following the functional programming principle of separating pure code from impure. For Ecto, that means keeping code that touches Repo separate from code that doesn’t. Working with contexts can help, as you can put the code that uses Repo into the context module and put the schema definitions into separate modules in the same namespace. We recommend putting the Repo module into a separate child application that its siblings can share when using umbrellas.