CQRS and Clojure

Using the CQRS pattern
The Command Query Responsibility Segregation (CQRS) pattern applies the command-query separation (https://en.wikipedia.org/wiki/Command-query_separation) principle by splitting the application into two parts, query side and command side. Query side is responsible for getting the data by only querying the state of the application, whereas command side is responsible for changing the state of the system by performing create, update, or delete operations on application data that may result in updation of one or more databases used by the application. Although the CQRS pattern is often used in conjunction with the event-sourcing pattern, it need not be tied to events and can be applied to any application

https://martinfowler.com/bliki/CQRS.html
https://blog.datomic.com/2015/11/cqrs-with-clojure-kafka-and-datomic.html
https://yuppiechef.github.io/cqrs-server/

Modeling core financial domains with RESTful + CQRS at Nubank
https://clojure-south.com/modeling-core-financial-domains-with-restful-cqrs-at-nubank/
https://github.com/onyx-platform/onyx-commander-example

From REST to CQRS with Clojure, Kafka, & Datomic - Bobby Calderwood
https://www.youtube.com/watch?v=qDNPQo9UmJA

"Commander: Better Distributed Applications through CQRS and Event Sourcing" by Bobby Calderwood
https://www.youtube.com/watch?v=B1-gS0oEtYc

Using Redis Streams to Build Event Driven Microservices and User Interface In Clojure
https://www.youtube.com/watch?v=30Odhss1xVA

No target file, test, or entry point is identified. Start by reviewing the repository's documentation structure and the linked CQRS and Clojure references; done means the issue has a defined documentation location and scope that follows the project's conventions.