► LEARN MORE: https://cnfl.io/microservices-101-module-1

In this video, you will see an example of how Tributary bank uses asynchronous events to enrich its domain and protect its fraud detection system from failures.

To learn more about Microservices, check out my Designing Event-Driven Microservices course on Confluent Developer: https://cnfl.io/microservices-101-module-1

Relying purely on synchronous request/response creates artificial limitations in a system. It requires commands to complete in milliseconds or users end up waiting unreasonable amounts of time. It also requires that all parts of the system remain operational. Should a failure occur, it can cascade back through complex chains of request/response operations. In a banking system, where transactions need to be completed instantly, this can be a significant problem. Fraud detection is a complicated process involving the application of machine learning algorithms, complex rules, and even human analysts. Assuming it can be completed instantly leads to a mismatch in expectations. Instead, designing a system that uses asynchronous events as the backbone of communication allows the system to take the time it needs to complete these complex processes, without leaving a user waiting on the other end.

RELATED RESOURCES
► Fraud Detection in Banking - https://www.cosive.com/fraud-detection-in-banking-guide
► Asynchronous Events - https://youtu.be/AJf_RRdbtEA
► Commands, Queries, and Events - https://youtu.be/G9LjwV8yDZU
► Point-to-Point vs. Pub/Sub - https://youtu.be/fay5_xP5IZk
► Scalable and Resilient Microservices - https://youtu.be/GXQxiMXfgew
► Event-Driven Architecture vs Request/Response - https://youtu.be/7fkS-18KBlw
► 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

CHAPTERS

00:00 - Intro

00:36 - Example: Purchasing Concert Tickets

00:57 - How to handle failure with Request/Response

02:04 - Producing events to be consumed by a microservice

02:37 - Moving the responsibilities into Apache Kafka

03:48 - Consuming events in the microservice

04:48 - Two-way communication between services

05:54 - Enriching the event model

07:26 - 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