Discussions @ https://docs.google.com/document/d/1wk7N9zggygz1Xx7qgx1aEt3niPpAEkRpdQi5i7k0Cj8/edit#
With the new GraphQL interface, we are able to implement multiple database as GUAC's GraphQL backend.
Right now we've implemented an in-memory database, and its tests, which will act as a conformance suite to the GraphQL backend. This puts us in a position to now have multiple DB implementations to the GraphQL interface.
Considerations of implementation of the backend will include:
- The ask from community members that are looking to run GUAC (prioritizing production use cases)
- The number of contributors who are interesting in implementing the use case
- The license of the DB libraries
- Usage factors / considerations / trade-offs
Note that the backends may be any type of database, from graph DBs (ArrangoDB / Neo4j) to more "traditional" DBs (Postgres, Spanner), or even a file system!
We'd like to get community input on what Databases they'd like to see in GUAC, with additional information about their use case and scale if available!
Discussions @ https://docs.google.com/document/d/1wk7N9zggygz1Xx7qgx1aEt3niPpAEkRpdQi5i7k0Cj8/edit#
With the new GraphQL interface, we are able to implement multiple database as GUAC's GraphQL backend.
Right now we've implemented an in-memory database, and its tests, which will act as a conformance suite to the GraphQL backend. This puts us in a position to now have multiple DB implementations to the GraphQL interface.
Considerations of implementation of the backend will include:
Note that the backends may be any type of database, from graph DBs (ArrangoDB / Neo4j) to more "traditional" DBs (Postgres, Spanner), or even a file system!
We'd like to get community input on what Databases they'd like to see in GUAC, with additional information about their use case and scale if available!