Event Modeling Step 3: Identifying the API of Commands and Read Models

► TRY THIS YOURSELF: https://cnfl.io/event-modeling-module-1

So far, we’ve considered the business narrative of Events that we’ll need to record on the backend, and we’ve envisioned how our users experience the system via the Interfaces it exposes on the front end. In this module, we’ll turn to the task of connecting these two worlds via an API of Commands and Read Models.

For a complete IMMERSIVE HANDS-ON EXPERIENCE: https://cnfl.io/event-modeling-module-1

—
CONNECT
Subscribe: https://youtube.com/c/confluent?sub_confirmation=1
Site: https://confluent.io
GitHub: https://github.com/confluentinc
Facebook: https://facebook.com/confluentinc
Twitter: https://twitter.com/confluentinc
LinkedIn: https://www.linkedin.com/company/confluent
Instagram: https://www.instagram.com/confluent_inc

ABOUT CONFLUENT
Confluent is pioneering a fundamentally new category of data infrastructure focused on data in motion. Confluent’s cloud-native offering is the foundational platform for data in motion – designed to be the intelligent connective tissue enabling real-time data, from multiple sources, to constantly stream across the organization. With Confluent, organizations can meet the new business imperative of delivering rich, digital front-end customer experiences and transitioning to sophisticated, real-time, software-driven backend operations. To learn more, please visit www.confluent.io.

#EventModeling #EventSourcing #StreamProcessing #confluent #kafka #apachekafka