Comment by tusharmath
2 years ago
Have you considered using https://tailcall.run It can automatically create a high performance graphql API.
2 years ago
Have you considered using https://tailcall.run It can automatically create a high performance graphql API.
Thanks for the pointer. Did you have a specific scenario in mind where this would be helpful?
Tailcall looks like something that could go in front of my library as an orchestration gateway.
However, as my library intentionally does not include any transport mechanism, you'd first have to expose it over HTTP (e.g. https://github.com/commitspark/example-http-express ). In my case, I actually have a couple of Next.js web apps where I load the library directly into the code instead and pass my queries to it without first going through HTTP.