the fact that you can write/mutate and read/query from the same call or transaction in #graphql.
powerful flexibility or anti pattern?
powerful flexibility or anti pattern?
by same call i mean same transaction, same request response cycle
i think im seeing it right?
you can mutate/write, and fetch what was mutated/written in the same round trip. OK
but you can't query/read, and then mutate/write anything "on the side", which would violate side-effect free functions, and idempotence. OK again
you can mutate/write, and fetch what was mutated/written in the same round trip. OK
but you can't query/read, and then mutate/write anything "on the side", which would violate side-effect free functions, and idempotence. OK again
just going off of Evans' DDD - Place as much of the logic / as possible into functions that return results w/ no observable side effects. Strictly segregate commands which modify state into very simple operations that don't return domain information. #sideEffectFreeFunctions
• • •
Missing some Tweet in this thread? You can try to
force a refresh
