When do you use API-first or events-first architecture? Is this a binary choice? This is a false dichotomy! A mental model is needed to frame the architecture, packaging, and programming choices for modern applications.
Varying degrees of combination of events and APIs can be used to design a system. Event notifications-based systems require an API callback to the source. CQRS and event-sourcing patterns, on the other hand, are on the complex end of the event-driven spectrum. APIs too have a maturity model, evolving with the adoption of reactive paradigms.
In this session, we’ll look at heuristics such as cost, latency, security, and external integrations that will influence implementation. Architects will learn actionable fitness functions to strike a balance between APIs and events to build sustainable architectures.