wundergraph-demo VS gradual-typing-bib

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

> with an implicit type contract (potentially generated) through the creation of these files

Racket is able to automatically convert static types of Typed Racket into contracts when values flow between typed and untyped worlds. This happens automatically and transparently, which means you don't have to worry about almost at all. One advantage Racket has over JS is the module system (well, it holds the same advantage over almost all the other languages), which allows typed and untyped code to reside in the the same file, yet have a clear boundary between them.

I can't find it right now, but there was a paper describing how it works. It's probably somewhere here: https://github.com/samth/gradual-typing-bib (if you're curious enough to read many tens of abstracts...)