Would it make sense to use CQRS or Sagas with a graphql server? I cannot really figure out where to place them.
Would a resolver fire an Event/Command, or would a service do or something completely different? Would sagas have a place there too? I am very confused about the whole event driven stuff and the various terms for the same thing but in different circumstances, like resolver and controller and so on.
#CQRS or Sagas and graphql?
verbal stone
essentially, having queries and mutations is some kind of CQRS already
crude dove
@verbal stone - My thoughts exactly. It's CQRS on the client, if you think of mutations as commands. The only thing that doesn't match is the fact that some things in a mutation do need to roll-back, if a process fails, and you can't do that on the client. No way, no how.
verbal stone
and on the server?