The Event-Driven Graph (composition)
What is an Event-Driven Graph and how is it composed?
Minimum requirements
An Event-Driven Graph (EDG) is best thought to be an abstract subgraph that facilitates Event-Driven Federated Subscriptions (EDFS). If a subgraph uses or defines any event driven directives (@edfs__request
, @edfs__publish
, and/or @edfs__subscribe
), it will be interpreted to be an Event-Driven Graph.
Definitions
The sourceName
argument, including the default value "default", must correspond to an equivalent property in events.sources of the router config.yml.
@edfs__publish
Argument name | Type | Value |
---|---|---|
subject | String! | The event subject. See subjects. |
sourceName | String! | The source name, which identifies the connection in the router config.yaml. If unsupplied, the default value "default" will be used. |
@edfs__request
Argument name | Type | Value |
---|---|---|
subject | String! | The event subject. See subjects. |
sourceName | String! | The source name, which identifies the connection in the router config.yaml. If unsupplied, the default value "default" will be used. |
@edfs__subscribe
Argument name | Type | Value |
---|---|---|
subjects | [String!]! | The event subjects (it is possible to subscribe to multiple events). See subjects. |
sourceName | String! | The source name, which identifies the connection in the router config.yaml. If unsupplied, the default value "default" will be used. |
streamConfiguration | edfs__StreamConfiguration | Configures a stream/consumer for a NATS connection. |
Compositional rules
The Event-Driven Graph is an "abstract" subgraph, so it must not define any resolvers. EDGs are also subject to special compositional rules.
Root fields
EDG Root fields must define their respective event directive and a valid response type:
Root type | Directive | Response type |
---|---|---|
Query | @edfs__request | A non-nullable entity object |
Mutation | @edfs__publish |
|
Subscription | @edfs__susbcribe | A non-nullable entity object |
Note that the edfs__StreamConfiguration
input object must always be defined to satisfy the @edfs__subscribe
directive:
Here is an example of a valid EDG mutation:
Attempting to return a type other than edfs__PublishResult!
from a EDG Mutation root field will result in a compositional error.
Root field arguments and event subjects
Arguments can be defined on a root field, which can then be passed to event subjects through an argument template.
The argument template should follow the period delimiter of your subject. The args
refers to the field arguments, which has its own period delimiter, followed by a name of a field argument. This argument name must match exactly to a corresponding field argument name.
Entity definitions
EDG entities must be "minimal stubs". This means that only the fields (and nested fields) that form part of its primary key should be included:
The primary key must contain the "resolvable" argument set to false.
Fields (including nested fields) must form part of the primary key
Fields (including nested fields) must be declared
@external
Here is an example of a valid EDG entity object definition:
Other definitions
The EDGs must not define any objects and fields that do not form part of an entity's primary key. Most other definitions are simply ignored, unless, for example, a root field requires an input object.
Last updated