Great explanation Mateus! What types or sizes of apps will benefit from an event driven architecture in your opinion?
Рік тому+1
Hey Silvan! Thanks man. I think any distributed application should at the very least consider EDA. For monoliths, I think there’s a lot you can take from an EDA approach - maybe not necessarily go 100%, but I find it easier to think about complex domain behavior as a series of rich, reactive events triggered by a command. It helps keep components loosely coupled and focused, it’s incredibly easy to extend and you get some fault tolerance. Unless I need something to be synchronous, I try to break down problems into small components that emit events.
Thank you for your reply@. I started using parts of this approach in an app I'm working on. I do love that I can subscribe to events and add features for example only for certain tenants. What do you think about event sourcing? Especially for the ecommerce example or a finance app, it might come in handy, but I was intimidated by the architectural overhead so far.
Рік тому+1
I gotta say that I'm not very familiar with ES. IMO it makes sense to use ES in financial systems and ecommerce - maintaining an accurate history of transactions/inventory is key, and it makes sense to have the current state derive from the events.
It's crazy how fast complexity grows after you start working with distributed services.
Great video!
Awesome introduction to EDA. I'd really love to see more about this kinda content, it would be really nice if you'd make it a series talking about EDA
I’ll add to my list :-)
Your videos are always great.
Glad you like them!
teu canal é mto bom! ja virou dos meus favoritos!
Oloco!! Nao tinha visto o teu comentário aqui. Fico feliz de ver vc por aqui. Valeu mestre!!
Great explanation. Thank you, Mateus!
My pleasure!
Awesome video, man! Async is a different world.
It sure is!
Great explanation Mateus! What types or sizes of apps will benefit from an event driven architecture in your opinion?
Hey Silvan! Thanks man.
I think any distributed application should at the very least consider EDA.
For monoliths, I think there’s a lot you can take from an EDA approach - maybe not necessarily go 100%, but I find it easier to think about complex domain behavior as a series of rich, reactive events triggered by a command.
It helps keep components loosely coupled and focused, it’s incredibly easy to extend and you get some fault tolerance. Unless I need something to be synchronous, I try to break down problems into small components that emit events.
Thank you for your reply@. I started using parts of this approach in an app I'm working on. I do love that I can subscribe to events and add features for example only for certain tenants.
What do you think about event sourcing? Especially for the ecommerce example or a finance app, it might come in handy, but I was intimidated by the architectural overhead so far.
I gotta say that I'm not very familiar with ES. IMO it makes sense to use ES in financial systems and ecommerce - maintaining an accurate history of transactions/inventory is key, and it makes sense to have the current state derive from the events.
muito bom, otima explicação, faz uma versão dublada hahahah
Tem no canal em português :-)
Great