What is the Listen to Yourself Pattern? | Designing Event-Driven Microservices
► LEARN MORE: https://cnfl.io/microservices-101-module-1
The Listen to Yourself pattern is implemented by having a microservice emit an event to a platform such as Apache Kafka, and then consuming its own events to perform internal updates. It can be used as a solution to the dual-write problem since it separates Kafka and database writes into different processes. However, it also provides added benefits because it allows microservices to respond quickly to requests by deferring processing to a later time.
To learn more about the dual-write problem, check out the Microservices 101 course on Confluent Developer: https://cnfl.io/microservices-101-module-1
RELATED RESOURCES
► What is the Dual Write Problem?: https://youtu.be/FpLXCBr7ucA
► What is the Event Sourcing Pattern?: https://youtu.be/wPwD9CQAGsk
► What is the Transactional Outbox Pattern?: https://youtu.be/5YLpjPmsPCA
► Microservices: An Introduction https://cnfl.io/3ZMt3up
► Event-Driven Microservices Architecture: https://cnfl.io/48FSYbj
► Migrate from Monoliths to Event-Driven Microservices: https://cnfl.io/3tsqlhu
► Get Started on Confluent Developer: https://cnfl.io/48FnKRB
CHAPTERS
00:00 - Intro
01:07 - What is the dual-write problem?
01:30 - What is the listen-to-yourself pattern?
01:51 - How does the listen-to-yourself pattern eliminate dual writes?
02:24 - When are the events processed in the listen-to-yourself pattern?
02:55 - Is the listen-to-yourself pattern eventually consistent?
03:43 - How can we deal with eventual consistency?
04:14 - How do we validate events?
05:02 - 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