PATTERN

CQRS is a pattern in which you have a different model for create/update/delete and a different one for read. The most applicable place for it is Event Sourcing – so you store events and for reading you use for example a database (which have been listening to the events and stores the current state). Worth …

CQRS – Command Query Responsibility Segregation Czytaj dalej »

When it comes to building an application we can react on some events (for example a user clicked the SAVE button, then we send request to backend and it does the job) and then forget about them (events). Event Sourcing is a different approach – you store events (like SavedForm(clickedBy, datetime, …)) and also have …

Event Sourcing basics Czytaj dalej »