r/graphql

After testing on Gitlab's huge full of unions schema and after fixing a lot of problems related to _all_fields fragment generation, graphlink was able to generate the client with more than 0.5 Gib of size.

This is obviously not something to brag about because no compiler is willing to help you compile that.i went through a lot of optimisation and found out some generated fragments are just huge.

I took a decision to add a configuration where a developer can set the max size for several reasons. The two most compelling ones are:

1- java has a limit for const strings which will generate a code that doesn't compiler (even though there is a work around to that.

2- Bandwidth and client size for typescript. None want to ship a huge client on a web app and none wants to send megabytes worth of data over the network for sending one request to a backend.

This being said I also encountered a lot of other issues that I fixed and guarded with tests. The hardest ones are java related because of its legacy.

Graphlink now can generate your full client just by writing pure graphql for 4 languages: Dart/Flutter Typescript Java and Kotlin.

I am planning to support other languages such as swift and maybe python (why not) in the future.

I am about to release version 5 that has been stress-tested on many known judge schemas such as GitLab GitHub Microsoft and twitch.

I will keep you updated.

Graphlik.dev

Start me on GitHub and open issues if you find any.

Cheers,

Reacting to Marc-André Giroux's blog post of the same name. Lmk what you think!

since all graphql action is a POST, what is the "META"/ Market standard to cache queries that would be automatically cached if it was a REST GET for example by Cloudflare ?

how to bypass this POST only downside?

I'm starting to post more GraphQL content. Eager for any feedback on the format!

A bit of honest context:

I recently had a conversation through the GraphQL network that got me thinking, and I'm now evaluating which direction to take a product I'm working on. So I'd genuinely value the experience of the people here.

The product is a GraphQL caching CDN / edge proxy: it sits in front of your GraphQL API and handles caching driven by your schema (with automatic invalidation), plus security and rate limiting.

The decision I keep going back and forth on: is something like this better run on-premise in your own infrastructure, as a managed SaaS, or do I need to offer both?

A few angles I'd love input on:

- If you run GraphQL in production, which would you reach for first, and why?

- For SaaS: is routing your query traffic through a third party an actual problem for you (compliance, data residency, internal policy), or a non-issue in practice?

- For on-prem: would you genuinely want to operate this yourself, or is "someone else runs it" part of the whole appeal?

And honestly, I'm also just trying to figure out how teams who'd care about this even discover tools like it. So if you remember how you found your current gateway or CDN, that helps too.

Blunt answers very welcome. I'm orienting, not selling.