14 Comments

Thanks for the mention Saurabh!

Expand full comment

For sure, I use them every time when I implement Stripe Checkout!

When you initiate a Checkout process with the items in your basket, specify your card number and other details, and click buy, the purchase doesn’t happen immediately.

Instead you have to listen to the events from a webhook and act when the “paid” event happens.

Expand full comment

This is great info, Akos.

These patterns are everywhere even though they might not appear to be so from the outside at first glance.

Expand full comment

Great article to understand Message queue and broker. Thanks

Expand full comment

Thank you for the feedback

Expand full comment

I helped design microservice architecture in my last company, and instead of such event driven architecture we used async calls, all APIs exposed via REST. I believe use of the things as explained in the article helps on a lot of places, and we shall start using them slowly so as to grasp good operation knowledge in the firm, which might be handy in next project.

Expand full comment

Thanks for the insight Kapil. I also think that a system should move into an event-driven approach only when needed.

If REST is working well for a project, it's a great choice and simple to reason about.

Expand full comment

Great article Saurabh! Thanks for the shoutout👍

Expand full comment

Thanks Amrut

Expand full comment

A very handy technology to decouple components in our systems. Personally i am a big fan of Azure Message Queues. A great article, Saurabh!

Expand full comment

Thanks my friend Daniel

Expand full comment

Thanks, this is helpful!

Expand full comment

Glad to share!

Expand full comment

The world we live in is Async; software should be following the same patterns!

Message Queues are the core of modern architecture.

Thanks for the article, Saurabh.

Expand full comment