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.
A worker can't cache or rate limit itself, it runs before cache [1] so every invocation of the url counts as a credit (free tier allows 1000 runs per minute / 100,000 per day / 3,000,000 per month)
Stellate always free tier can front run your free graphql worker with 100,000,000 extra CDN hits - a possible saving of $50/month if just on paid workers. What's the catch? attribution?
Could you please stop posting like this? It's fine to make your point once but this sort of unsubstantive harangue doesn't add anything interesting, and it's nasty.
I still think that 30M is a bit too much for a problem that is already solved.
We will see what they are able to do with the funding.
Good luck to the team