Messages between microservices come in three different flavors: Commands, Queries, and Events. Commands change the state, queries request the state, and events share the state. When designing microservice communication patterns, it is important to understand the role of these messages. Following a clear set of rules can help ensure consistency and clarity within your system of microservices.

Check out Confluent Developer to find more information and courses on how to build event driven microservices: https://cnfl.io/48FnKRB

ADDITIONAL RESOURCES
► Migrate from Monoliths to Event-Driven Microservices: https://cnfl.io/3tsqlhu
► Event-Driven Microservices Architecture: https://cnfl.io/48FSYbj
► Microservices: An Introduction https://cnfl.io/3ZMt3up
► Asynchronous Events: https://youtu.be/AJf_RRdbtEA

CHAPTERS

00:00 - Intro

00:20 - Principle of Least Surprise

00:49 - Commands

01:09 - Responses

01:31 - Async Commands

02:00 - Queries

02:46 - Events

03:14 - Ignoring Events

03:45 - Async Events

04:27 - Delta Events

05:20 - Fact Events

05:46 - Data Coupling

06:15 - Closing

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.

#microservices #apachekafka #kafka #confluent