1
1
# Execution
2
2
3
- GraphQL generates a response from a request via execution.
3
+ GraphQL service generates a response from a request via execution.
4
4
5
5
:: A _ request_ for execution consists of a few pieces of information:
6
6
@@ -144,8 +144,7 @@ executing the operation’s top level selection set on the mutation root object
144
144
type. This selection set should be executed serially.
145
145
146
146
It is expected that the top level fields in a mutation operation perform
147
- side-effects on the underlying data system. Serial execution of the provided
148
- mutations ensures against race conditions during these side-effects.
147
+ side-effects on the underlying data system.
149
148
150
149
ExecuteMutation(mutation, schema, variableValues, initialValue):
151
150
@@ -174,7 +173,7 @@ Subscribe(subscription, schema, variableValues, initialValue):
174
173
{MapSourceToResponseEvent(sourceStream, subscription, schema, variableValues)}
175
174
- Return {responseStream}.
176
175
177
- Note: In large scale subscription systems , the {Subscribe()} and
176
+ Note: In a large- scale subscription system , the {Subscribe()} and
178
177
{ExecuteSubscriptionEvent()} algorithms may be run on separate services to
179
178
maintain predictable scaling properties. See the section below on Supporting
180
179
Subscriptions at Scale.
@@ -222,7 +221,7 @@ must receive no more events from that event stream.
222
221
223
222
** Supporting Subscriptions at Scale**
224
223
225
- Supporting subscriptions is a significant change for any GraphQL service. Query
224
+ Supporting subscriptions is a significant challenge for a GraphQL service. Query
226
225
and mutation operations are stateless, allowing scaling via cloning of GraphQL
227
226
service instances. Subscriptions, by contrast, are stateful and require
228
227
maintaining the GraphQL document, variables, and other context over the lifetime
@@ -396,7 +395,7 @@ completion before it continues on to the next item in the grouped field set:
396
395
For example, given the following selection set to be executed serially:
397
396
398
397
``` graphql example
399
- {
398
+ mutation {
400
399
changeBirthday (birthday : $newBirthday ) {
401
400
month
402
401
}
@@ -418,7 +417,7 @@ As an illustrative example, let's assume we have a mutation field
418
417
we execute the following selection set serially:
419
418
420
419
``` graphql example
421
- {
420
+ mutation {
422
421
first : changeTheNumber (newNumber : 1 ) {
423
422
theNumber
424
423
}
0 commit comments