# Writing modular / composable phoenix code

**URL:** <https://forum.elixirforum.com/t/writing-modular-composable-phoenix-code/31019>\
**Category:** Questions\
**Tags:** umbrella, phoenix, dry, software-design\
**Created:** [April 27, 2020, 12:49pm UTC](https://forum.elixirforum.com/t/writing-modular-composable-phoenix-code/31019 "2020-04-27T12:49:57Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![fireproofsocks](https://forum.elixirforum.com/user_avatar/forum.elixirforum.com/fireproofsocks/32/7669_2.png) [@fireproofsocks](https://forum.elixirforum.com/u/fireproofsocks)\
**Post date:** [April 27, 2020, 3:50pm UTC](https://forum.elixirforum.com/t/writing-modular-composable-phoenix-code/31019/4 "2020-04-27T15:50:44Z")

</div>

> [@magosi](#):
>
> Also, why is this not a frequently asked question? Do other people just write their apps from scratch?

I have re-used modules many times from different Phoenix projects: they are very portable. The only wiring that was needed to install them was to reference them somewhere (e.g. in a plug or a controller). It’s not a plug-and-play as, say, a WordPress plugin, but 1 size doesn’t always fit all. Sometimes the “simplicity” in having things as easy to install as a WordPress plugin backfires when you need to customize it, and jail-breaking the functionality out of its carefully defined environment is harder than just wiring in more generic modules.

Phoenix Plugs might be the middle ground there: they revolve around a well-documented struct and are easy enough to reference in various projects. They can be used to handle an entire request, from soup to nuts, so I would recommend giving them a look before trying to balance multiple Phoenix apps under an umbrella or some other more sophisticated solution.

---

_[View the full topic](https://forum.elixirforum.com/t/writing-modular-composable-phoenix-code/31019)._
