Integrating Our OTP Dependencies into Phoenix—Continued
Explore methods for integrating OTP dependencies into Phoenix applications by using path and umbrella project structures. Understand the trade-offs in development independence, tooling, and dependency management. Discover how Phoenix contexts relate to OTP project organization to effectively assemble and organize your Elixir components.
Using external path dependencies
Suppose we want to work with an external dependency but want the convenience of keeping everything in the same repository. In that case, we can take the same approach we did with persistence and use a poncho-style dependency. Poncho dependencies have an ever-so-slight coupling to their parent projects called an organizational coupling.
Benefits
The benefits of this are development independence with reduced ceremony:
-
We’ll be able to evolve interfaces side by side.
-
Since all of our dependencies are in the same repository, we’ll be able to keep them in sync better. ...