Skip to content

Commit

Permalink
GraphQL ADR: Refactor the answered server question
Browse files Browse the repository at this point in the history
By means of refactoring that question item along with surrounding ones.

(As this was a previously left-over question that was answered already.)

Signed-off-by: Marco Miller <marco.miller@ericsson.com>
  • Loading branch information
marco-miller committed Mar 15, 2022
1 parent d580b6a commit 0b9367e
Showing 1 changed file with 6 additions and 8 deletions.
14 changes: 6 additions & 8 deletions doc/adr/0002-GraphQL.md
Original file line number Diff line number Diff line change
Expand Up @@ -120,14 +120,12 @@ According to the [Pluralsight course][course],

#### Centralized server

Possible for `trace-server` servicing?

From the [Pluralsight course][course]:

* GraphQL Server able to fetch data from ***legacy system***(s).
1. By means of writing per-field Resolver functions.
1. Batched (optimized) resolving supported; [batching][batch].
1. API gets itself documented through the developing GraphQL schema.
* Possible for `trace-server` servicing, as this ADR shows [next](#proposed-change).
* From the [Pluralsight course][course]:
* GraphQL Server able to fetch data from ***legacy system***(s).
1. By means of writing per-field Resolver functions.
1. Batched (optimized) resolving supported; [batching][batch].
1. API gets itself documented through the developing GraphQL schema.

## Decision

Expand Down

0 comments on commit 0b9367e

Please sign in to comment.