Architectural pattern for communication between modules
This is a general question, looking for some direction.
I'm thinking about a SPA that will grow large with many complex modules that will need to interact.
For example, if a user modifies data in some module, which should be reflected in another module (non-trivially), the catch being, both modules should not know of each others existence. I don't want to them to communicate directly (e.g. mutual events, shared data, juggling callbacks, etc).
Is there some kind of pattern that works well for this in AngularJS? Most articles I find describe on too low a level approaches to this (such as events, callbacks, watches, etc.) But if used ad-hoc, the UI becomes chaos.
Posted Apr 15, 2016, 1:24 AM UTC
12