Opportunities and Pitfalls of Event-driven Utopia

[@jasonmeyer495]

He's such a fun presenter to listen to. Very engaging. One of the best in this channel.

[@duyibest]

Very well done. Thank you!

[@sujeewae6599]

Great content. I didn't feel I just spend 50 minutes. Magical delivery.

[@iamthesamrus]

Great talk, thank you!

[@srikanthjnr]

Great overview on Event Sourcing architecture...

[@carmineingaldi47]

The talk is a nice overview of advanced concepts regarding event-driven architectures, but I don't agree on presenting event sourcing as en evolution of EDAs. Event Sourcing is just an architectural pattern, an implementation detail that engineers can use to solve specific problems. Keeping state in a datastore doesn't conflict with the idea of propagating side effect across processes thrugh async messages that have an event semantic

[@Hangar1318]

I think RocksDB was written by Facebook, not Netflix

[@osamaa.h.altameemi5592]

That was really good. Thx a ton. One quesion though why go with rocksdb and not redis or sqlite.

[@NareshKumarD107]

good talk... informative

[@rambo4014]

How to use outbox pattern if we want it as a real time use case?

[@craigmunday3707]

Really nice talk

[@CameronFlint07]

Awesome talk, thanks!

[@allanhouston22]

I like the original project, Activiti BPMN, more

[@JoelBondurant]

RocksDB rocks.

[@jayak3768]

Very abstract. Following an example would have been better.

[@pohjoisenvanhus]

So it's immutability like in pure functional programming and booting up from an image like SmallTalk and other old languages? lol