Getter methods retrieve state, while setter methods change state. We all know that. HTTP GET requests retrieve state, while HTTP POST requests change state. We all know that. Then why have we built so many applications with a single object model, blatantly ignoring this separation? Turns out that creating a separate model for reading and writing makes a lot of sense. But how can we introduce this concept into legacy applications? This presentation shows how to do it, and what is in it for you.


Please login to leave a comment

The information was there and it's obvious that he talks from experience and is very knowledgeable about the subject. However somewhere around the middle of the talk he started going back and forth with his slides and I got completely lost.

I expected more concrete stuff about CQRS witout event sourcing (ES wasn't metioned in topic or description for that presentation). Would be nice to see some code examples. But overall it was quite great presentation