Warren Parad
1 min readDec 1, 2019

--

I’ve seen this happen so many times. CQRS is an implementation detail, like so many other things, async updates, which cloud provider you are using, or if your database is relational or document store. You can’t break apart an implementation into two services, it never works. Microservices are built around logical business concepts (ones that are purely API driven or something less complex like a UI), breaking apart the internal implementation into two services will always cause a problem.

The simple solution in this case was just to combine your two services, since it doesn’t make sense for two different services to exist to serve the resources (this isn’t even RESTful), reads(GETs) and writes (PUTs) should be on the same resource server. If the logic was contained in only one service then it becomes an easy activity to handle the failure modes discussed.

--

--

Warren Parad
Warren Parad

Written by Warren Parad

CTO and Founder Authress, Complete Auth for B2B.

No responses yet