You’re building a new system and two members of your team propose alternative architectures for sending notifications. The first developer proposes a push model: bounded contexts should instruct the notifications context to send a notification. The second developer dislikes the push model and proposes a choreographed solution: when bounded contexts raise events Notifications should listen and determine when to send a notification. This article explores the DDD perspective on this scenario and discusses the advantages of decoupling domain-specific and domain-generic bounded contexts to enable effective architecture design and long-term evolution.
