Date: Sun, 07 Feb 2021 16:33:20 GMT
<p>Reads and Writes don’t have to live in the same database, data model or even the same service. Let us discuss CQRS</p> <p>no separation</p> <p>one service that does read/write</p> <p>partial separation</p> <p>You can keep one service but backend have multiple connections with different users same database</p> <p>full separation</p> <p>Read services / write services</p> <p>two databases OLAP / OLTP</p> <p>Pros</p> <p>scalability</p> <p>security</p> <p>Cons</p> <p>complex and very hard to follow, what we see with microservices..</p> <p>resources</p> <p>https://martinfowler.com/bliki/CQRS.html</p> <p>http://codebetter.com/gregyoung/2010/02/16/cqrs-task-based-uis-event-sourcing-agh/</p>