Organization of a large number of mutations

We have an installed system that does not have an open API, and we evaluate GraphQL as a possible solution. We have a dozen different types, relationships, and possible actions / mutations.

From what we read and from our experiment, we can only have one root root, and all mutations should be listed here. We have many modules, each of which has many objects and is available for each of them.

How do people organize a large number of mutations? We are trying to find examples of large applications using GraphQL that we can learn about.

+4
source share
1 answer

. . :

mutation {
    users { 
        addUser(name: "Foo")
            id
        }
    }
}

, ,, Root.

https://github.com/graphql/graphql-js/issues/221

@LeeByron

, .

+1

Source: https://habr.com/ru/post/1654831/


All Articles