CQRS is simpler than you think with C#11 and .NET 7! - Oskar Dudycz

[@MerrionGT6]

"The most important is to be able to isolate the business logic.." +100!

[@MerrionGT6]

Also "CQRS enables multiple databases but does not require more than one database" also +100

[@event-driven]

Thanks, @@MerrionGT6 ! My main goal behind this talk was to show CQRS in nutshell and bust common myths. Especially the misconception that CQRS adds overhead. That's why I showed that with maximum simplicity, single table and ORM. I believe that's CQRS benefit that you can start small, and expand when and where you need without risking breaking the whole app. 🙂

[@vincentcifello4435]

This is the most sensible review of. CQRS(and programming in general) available. Thank you Oskar! Looking forward to exploring your website.

[@z0nx]

Nice talk. Didn't expect to see actual Funcs in a csharp talk, that's like the most overlooked ways to abstract out implementation details! I feel like this is what is lacking in most of the talks: simplicity.

[@event-driven]

Thanks @z0nx, I'm glad that you liked it. It was intention behind my talk to show that CQRS is about simplicity, and also new C# and .NET features allow us to write code simpler. Better to start with less code and add it when it's needed, instead of the other way round.

[@vallJune]

Thanks Oskar for cool talks. Do you have those example in github what to take a look out of corner of my eyes?

[@fred.flintstone4099]

Wouldn't it possible to validate the SKU in the constructor for the record? Records can have constructors.

[@cheeseburger1884]

this guy is Jimmy Bogard on steroids

[@event-driven]

That's one of the best compliments I could get 😅