the n+1 graphql problem is more difficult than most people realize. graphcdn makes it incredibly easy to globally scale a backend application with dynamically changing queries. of course, it _is_ possible to hack together some clever cloudflare workers (i've tried), but it gets increasingly difficult to actually have the cache hit if you have a ton of changing fields (with nested values). then, there's the sunk cost of managing/tweaking everything if you're a small team. I also really like how clean and useful the visualizations are.
it's not for every use case, but it's clearly useful for the thousands of companies that have signed up and are paying them. :)
The example they give is basically Zapier for data?
"For example, you might want to figure out if the customer who just submitted a ticket is a high-value customer by checking the matching subscription in Stripe's data and whether there are any associated high-value deals with that customer's company in Salesforce."
No guarantees on traction, but folks doing integration work have gotten a fair bit of use. So as always - this might fail.
it’s just a proprietary caching proxy
“impressive business” is entirely subjective