Actors or Not: Async Event Architectures

[@anonymous8164]

Great video! Thanks for sharing your experience!

[@amenostalgique]

Good presentation. It helped me to validate my own intuitions. Thanks

Maybe I'm confusing things but this events adapter is like simple Saga that by definition consumes events and produces commands. Of course, it does more as it also translates and serializes/deserializes but still if we talk about DDD maybe its good to name things as they are in DDD.

[@danielpapukchiev3754]

I think the event adapters are in an interface layer - translating incoming events / commands from different inputs to the application interface inputs

[@hazemashraf5131]

i love this channel thanks alot

[@tomclancyya]

Спасибо за доклад, мощно все раскидал! До сих пор оч актуально

[@japrogramer]

So this is like celery and redis or messagemq ...

[@TheRodmena]

It's obvious while they are using Erlang as networking layer, they are not confident enough to leverage the whole Erlang OTP to solve almost all of the problems they have. How sad.

[@ArchimedesTrajano]

3:57 I solved the Service Discovery problem by simply using Docker Swarm and have DNS.

[@rahmatalbariqi6236]

nodejs implementation in python