BDM Architecture Principle 13: Principle: Adoption of Event-Driven Architecture Statement: Preference will be given to event-driven architecture to help build decoupled, responsive, adaptive and resilient solutions. Rationale: Modernization of digital channels and services, as well as planned advances in service delivery and common benefit processing, require ability to access data and process events and transactions in (near) real time. Solutions and services need to be designed to “react to events” and process them in (near) real time where desirable and to the extent possible. This type of architecture adds a layer that further decouples architecture components, making the overall architecture more adaptive and resilient. Implications: • Key objective is to move from batch to predominantly (near) real-time services and transactions. • Every integration should be considered for event driven approach. BDM will implement the most appropriate pattern for each integration with a view to move to event-driven integrations whenever this approach is aligned with the business processes the integration enables. • We will assess supporting solutions and dependencies for their ability of being event driven and can participate without added complexity. • Best practices and lessons learned from previous successful implementations of these technologies will be consulted prior to making the decision. • We do not recommend “Everything is an Event” approach. Complementary integration patterns exist and will be considered for integrations that are not natively event-driven. Data integration technologies are available too! • Selection and implementation of an Event Broker and Messaging Platform becomes high priority for Tranche 1. • Caveat: Cùram SPM includes OOTB batch processes that need to be implemented as defined by the platform. No previous implementations of Cùram were based on event driven architecture. • Caveat: This type of architecture requires highly-available and resilient network and infrastructure. Cost may increase. • Caveat: Will require high transaction rate through SCED which raises performance and bandwidth concerns. BDM EA WG: The principle is well received and supported by the architecture community. Despite caveats, this is a good principle to have to communicate desire to move from batch to predominantly real-time client services and transaction processing. Recommendation: Accept