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

CQRS is often perceived as an over complex pattern with a lot of redundancy and ceremony. Too often it's explained as pushing towards multiple databases, eventual consistency, DDD, and Event Sourcing. In this talk, I will show that it's the opposite.

During live coding, I will show how CQRS can help in tackling the layered architecture complexity. I'll build a simple but real WebAPI. Then I'll spice all of that with all the goodies from C#11 and .NET 7 to help achieve that. Records, Nullable Reference Types, Endpoints etc. The main focus will be on CQRS and pure .NET, not Event Sourcing, or DDD.

Oskar is a developer, technical team leader, and architect. Oskar started a career before StackOverflow existed. For over 14 years, Oskar has been creating systems close to the business process. Oskar believes that Event-Driven Architectures and Event Sourcing are great ways to achieve that.

This session was recorded at Swetugg Stockholm 2023, Swetugg is run by a group of volunteers with different IT backgrounds with a common denominator: A passion for creating good software and better software developers, no matter if you are just starting your journey or have been writing code since the beginning of unix time.

[vincentcifello]

This is the most sensible review of. CQRS(and programming in general) available.

Thank you Oskar!

Looking forward to exploring your website.

[MerrionGT]

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

[fred.flintstone]

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

[vallJune]

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

[znx]

Nice talk. Didn't expect to see actual Func<_>s 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.