- Some similarities to Observer and Observable pattern(s)
- Could you use an Oberserver implementation as the middle of a pub/sub implementation? ie Publisher -> Observer -> Subscribers
- Order of subscribes and publish makes for bootstrapping/bootup order requirements. Inexplicit coupling that's hard to debug
- Data is the coupling - how to version?
- Informational only
- If you need certainty, acknowledgement is needed. (By directional messages?)
- Discrete parts of a system - allow scaling of team(s) so each work on their own part given a contract
- Pusherapp
- Pubnub
- npm: pubsub-js (and the other 10m)