Read GraphQL mutation result while using event sourcing

Viewed 488

In recent project we are trying to adopt an event sourcing pattern. For backend API we decided to use GraphQL. As far as I understand changing data in this type of architecture should be asynchronous. On the other hand, GraphQL mutations usually return modified data. How to connect those two words?

To be more precise, let's consider user register mutation. How, for example, FE can tell the user that the selected user name is taken?

0 Answers
Related