Microservices architecture | Asynchronous systems ft. Vaughan Sharman | 11:FS Explores Lightboards

Let’s say an organisation has migrated their mainframe services to the cloud, and that they're now looking to move from a monolithic architecture to microservices. They'll likely start with a request-reply (synchronous) integration, with just a few services.
As the business scales, they may find that the synchronous architecture strains. As more services are added over time, more dependencies come into play. This increases the chances of a cascade of failing calls taking place when there is a notable event in the business - such as a sudden influx of requests.
In this scenario, it’s worth moving to a slightly different model of microservices patterns. Asynchronous communication removes the dependencies between services, and can make it far easier to plan for, and handle, large unexpected amounts of volume by eliminating the need for services to wait for a response from each other. It introduces a message bus that facilitates communication consistently across services, lifting those dependencies.
In this 11:FS Explores: Lightboard Edition. Vaughan Shaman takes us through how asynchronous systems work, and their advantages, and how it can remove potential bottlenecks.

[@bamne123]

In a synchronous architecture, service A is depends on the output of the B. Can you help me understand how Service A will know to execute next set of instructions after Service B puts its output on the Bus/Queue in asynchronous architecture.

[@JayPatel-ne6jf]

Using some sort of callback is the only option.

[@kuttikrishnankodoth3298]

what if i want to display a response in UI , say for instance i have a complex use registration UI upon button click calls several microservices .. say i made all the microservices async like you said .. how am i going to tell the ui that the operation is successful ? or erored out ? every one is very eager to talk about making asynchronous but no one really answers this question.

[@namazbekbekarysuly9112]

This is great visualization. Thanks for the content.
The only thing is that blue marker doesn't contrast very well when the presenter is behind the schema.

[@abhisheksinghal1667]

+1

[@TungNguyen-jf5bj]

Very good explanation

[@mohammedramadan3480]

isn't that mean, when a request comes in, I should respond immediately to user with something like ( your request is in processing ) ?

[@Ddos2212]

The marker screeching is unbearable