Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

2
  • Integration is a concern of each module's Application package/layer. ie: Service Container Dynamic Bindings + Routes. As for cross-module relationships - if another separated module (ProjectManagement for example) needs to perform some type of Authentication within it's own respective API than I include the "Access" module's Application layer as a listed dependency. The package manager then retrieves any remaining nested dependencies. Access Application -> Access Infrastructures -> Access Domain so I can perform the necessary work. Commented Mar 21, 2016 at 5:19
  • 1
    Yes I think that kind of cross domain linking is probably a mistake. You are likely to get circular dependencies Commented Mar 21, 2016 at 8:04