GraphQL and CQRS, a Perfect Fit?

Gerard KlijsAxonIQ, Software Engineer

With an CQRS architecture, the write and read model are separated. The read model is also eventually consistent. This makes it hard to implement GraphQL mutations as they are implemented usually. We can't directly return the updated entity, as that's not available in the write model? But do we need to return this, or can we get away with just returning if the mutation was successful? Are there ways we can still return the updated entity? We will dive deeper into this, and also at the consequences for queries, and subscriptions.