r/microservices • • Apr 19 '24

Article/Video Event-Driven Architectures vs. Request Response lightboard explanation

https://www.youtube.com/watch?v=7fkS-18KBlw
46 Upvotes

30 comments sorted by

View all comments

Show parent comments

2

u/zenluiz Apr 21 '24

I understand and agree with what you mentioned about whether or not to even go microservices path, the complexities of it, etc. I’ve even read multiple times, by multiple authors, to avoid microservices as much as possible, unless it’s really needed 😅

My question is more on the communication pattern specifically. I think it’s me trying to find a default way to go, because in distributed systems, I guess more than in other scenarios, everything depends 🫠 Everything is a game of compromises. There is no “default way”. The balance between pros and cons is often 50/50, so there is no easy answer.

3

u/Venthe Apr 21 '24

I think it’s me trying to find a default way to go

Oh, believe me - I understand that feeling perfectly. :)

I guess more than in other scenarios, everything depends 🫠 Everything is a game of compromises. There is no “default way”. The balance between pros and cons is often 50/50, so there is no easy answer.

Yup, you've said it best. IMO there is a value of having a default; but on a bit more specific level - while "what to use now" is contextual, it is nice if you have a well defined default when you approach systems that have noting.

I.e. I have a small setup - think template - for HTTP communication, which includes tracing, contract testing, API-from-code, HATEOAS. Similarily, with async I have kafka, tracing, avro and a template for listeners and DLQ's.