Asynchronous Events | Designing Event-Driven Microservices

Asynchronous events are a communication pattern that is used to build robust and scalable systems. These events are often pushed through a messaging platform such as Apache Kafka. Among their benefits are the ability to optimize resource usage, more flexibility for scaling, and new ways to recover from failure without losing data.

RELATED RESOURCES

CHAPTERS
00:00 - Intro
00:27 - Synchronous Calls
01:05 - Cascading Failures
01:37 - Cascading Delays
02:53 - Asynchronous Events
03:46 - Reduced Coupling
04:22 - Increased Reliability
04:56 - Slow Consumers
05:24 - Closing

--

ABOUT CONFLUENT

#microservices #apachekafka #kafka #confluent

[renedekat]

It's a great solution for many use cases. One where I can't see it working (emphasis on "I"), is when transferring or withdrawing money from an ATM. You need instant feedback whether or not you have sufficient funds. The subsequent transaction can be handled asynchronously, but the funds check needs to be synchronous.

[RicardoSilvaTripcall]

I've worked on a system, where we had to call ten other services to make a loan payments simulations, all services had to be call synchronously because most of them depended on data of the previous response to make the next request, I think in this scenario, it was almost impossible to make it asynchronous, because the final response had to be shown to the customer on the website, we started to face some timeouts issues, and the only thing we could do was to change and improve some calculations made throughout the workflow ...

[randaldurayhim]

I think not every call to a microservice can be turned to event-driven. what if i'm calling another service for a query into the service's database?