cqrs is great, but you need to emit changes in your system in consumable way in order for cqrs to work since it is based on reaction to these changes and buildi

cqrs is great, but you need to emit changes in your system in consumable way in order for cqrs to work since it is based on reaction to these changes and building the "views" from them. not fun to implement, a lot of code is needed, especially if you are doing event sourcing and not just some simple event logging. but it is VERY powerful design, in conjunction with event sourcing. it essentially removes strict schema from your system and you can have fluid data storage and perform various analytical tasks with past data and not being locked only to current data. very powerful! it is a dream to have but a pain to implement.