This is something I have also thought about… Eventually went down the path of SQL with apache calcite + jax rs….
You can achieve similar outcomes (get multiple resources in one request, compatible evolution…) Here is a quick writeup + poc: https://github.com/zolyfarkas/jaxrs-spf4j-demo/wiki/AvroCalciteRest <https://github.com/zolyfarkas/jaxrs-spf4j-demo/wiki/AvroCalciteRest> There are some advantages to SQL… like a lot less docs to read/write… —Z > On Feb 15, 2019, at 6:26 PM, Mike Thomsen <mikerthom...@gmail.com> wrote: > > My team is fairly experienced with Avro, and we were wondering if anyone > has thought about/tried/accomplished a process to use existing Avro schemas > as the foundation for a GraphQL API. I didn't find much that was promising > when I searched on it, but I'd like to hear if anyone has thought about > ways to make this work. > > Thanks, > > Mike
