wundergraph-demo VS graphql-zeus

If you want to follow along and experience these patterns yourself, you can clone this repository and play around.

Thanks to our GraphQL Operation Compiler, we're in a unique position that allows us to only send the "Operation Name" as well as the "Variables" to the server. This approach makes our GraphQL API much more secure as it hides it behind a JSON-RPC API. You can check out an example here, and we're also open sourcing the solution soon.

I've been working on this problem for a few years actually. What I came to realize is that 99% of all (GraphQL) APIs are private, meaning that we don't expose them to a 3rd party. One aspect of private GraphQL APIs that is almost always true is that the access patterns don't change at runtime, meaning that when deployed to production, the Operations don't change any more. What this means is that in production, we don't really need GraphQL. We don't benefit from GraphQL in production anymore, as we're not writing dynamic Operations. Instead, we could compile the GraphQL Operations that we need into a REST API. This step adds extra complexity, but reduced the attack surface and improves performance. To reduce the overhead, I've created a developer tool. WunderGraph! It compiles your GraphQL APIs into REST Endpoints and generates typesafe clients for them. The DX is still the same, you write GraphQL Operations and use a typesafe client. But behind the scenes, it's just REST. We even generate a Postman Collection, so you can easily share the generated API with your team. Here's a demo if you'd like to try it: https://github.com/wundergraph/wundergraph-demo We're open-sourcing the solution very soon! =)

Alternatively, you can also just run "wunderctl init --template nextjs-starter" to start with the NextJS template. (Obviously you need to install it first: yarn global add @wundergraph/wunderctl@latest)

We're going open source with this solution soon. So, any feedback is appreciated! You can also join our discord and shoot questions. =)

[0]: https://github.com/wundergraph/wundergraph-demo

WunderGraph: click here!

It's already possible. Here's a demo: https://github.com/wundergraph/wundergraph-demo

Shameless plug, you can use Federation, Schema Stitching, REST APIs, etc. all together and even transition from one to the other, here's a demo: https://github.com/wundergraph/wundergraph-demo

When I asked this in StackOverflow over a year ago I reached the solution of using graphql + graphql-zeus.

You can think of GraphQL Zeus as Prisma for the frontend: it writes GraphQL queries out of JavaScript objects and produces the proper return types.

graphql-zeus: You write your graphql queries using a JavaScript object like syntax. Looks cool, but I think it's too big of a burden on the team to have to give up writing queries using graphql-tag/gql.

https://github.com/graphql-editor/graphql-zeus generates subscription code and in generated code you'll find simple apiSubscription function you can use/copy

You can do this with GraphQL too:

https://genql.vercel.app/

https://github.com/graphql-editor/graphql-zeus

I did a 5 min talk about these newer breeds of codegen tools (where it's a single client SDK that does automatic return type inference based on the input args), it's really neat:

https://www.youtube.com/watch?v=7n3MeMFHiMk