Feature

Keep broker schemas in runtime after registering, deregistering and swapping.

Feature

Enable an internal broker API, to be able to consume schemas without accessing directly redis and in a controlled way by the broker.

Implement:

• schema visualizing data
• see triaged schemas
• see comparisons and outcome results for each recombination (actual + any triaged schema outcome)

Feature

Design an API endpoint, probably WS-based, to retrieve a real-time hot path graph of the query/mutations usage across all gateways at the same time.

Hot-path should record the GraphQL queries AST accesses required from the client's side to the properties

Probably this feature will require some internal inter-gateway communication. (in a separate issue)

Feature

Enable an internal API to be consumed to retrieve some gateway metrics. Such as

• see clients connected to the gateway (schemas + online + URLs)
• queries hot path (separate task)

Feature

We want brokers to maintain a runtime schema in some cases.

Problem

As the brokers are distributed, if any of them do some schema swapping or evolution (nonbreaking change) there's no way for other brokers to update their runtime state.

Whatodo

Study a solution to sync between all the brokers upon any node change.