10 Comments
User's avatar
Petar Ivanov's avatar

Great post, Saurabh! 🙌

Expand full comment
Saurabh Dashora's avatar

Thank you Petar!

Expand full comment
Raul Junco's avatar

The communication pattern can make or break your application.

Simply explained, Saurabh!

Expand full comment
Saurabh Dashora's avatar

Indeed!

Thanks Raul

Expand full comment
Bruno Taboada's avatar

I personally have used all of them. However, when

it comes to Event-driven model, systems tend to

be more complex to understand and follow as on

many occasions, business logics need to broken

into discrete events and data

flow might be a lot more distributed.

Expand full comment
Saurabh Dashora's avatar

Absolutely Bruno.

Event-driven flow can become hard to reason about.

Expand full comment
Daniel Moka's avatar

A solid post with the fundamentals, loved that, an excellent write up Saurabh friend!

Expand full comment
Saurabh Dashora's avatar

Thanks Daniel!

Expand full comment
Shrikant Khadilkar's avatar

you could also add web sockets to this as an example of bi-directional communication pattern

Expand full comment
Akos Komuves's avatar

Excellent overview, Saurabh! Most of the time, I've used all patterns 1), 2), and 4) (if I correctly assume webhooks fall under 4).

3) needs more infrastructure than the other 3, so I've avoided it.

Thanks for the shout out! 🙇‍♂️ Glad you enjoyed my article!

Expand full comment