[timsuchanek]

Thanks @hcentelles, that's great to hear and gives us validation that there is a need!

Compared to Apollo Cloud: We're mostly focused on the caching part right now and have a different architecture where we are in your stack. Apollo runs a sidecar next to your application. We are a proxy in front of your API.

When it comes to the analytics part - which Apollo rather calls metrics, I think Apollo gives you field-level information, while we for now just have query-level information. However, we are fully server agnostic - you don't need to use Apollo Server. Any GraphQL API works. You just need to switch the URL in your clients. We even have customers just using the analytics part for now and disabling the caching in the beginning.

For the pricing: That is correct - you'd have about 50mio requests a month, so $500. However, the pricing there is not set in stone and we're happy to give you an early discount. Just contact us at [e-mail].

Right now only outside requests count as a request, no matter if cached or not. Purging calls might also count in the future.

[hcentelles]

Thanks for the quick (good news) answer. I’ve more questions

We use Apollo client, I’m worried about 2 specific features of it:

Batch queries [1], we’re currently using it.

Persisted queries [2], we’re planning to using it.

Are those compatible with GraphCDN?

1. https://www.apollographql.com/docs/react/api/link/apollo-lin...

2. https://www.apollographql.com/docs/react/api/link/persisted-...

[mxstbr]

We "support" batched and persisted queries in the sense that we don't break them, we pass them through to your origin, but we don't currently analyse them. Caching / analytics support for both of them is on our roadmap[0] in the near-term for sure!

[0]: https://graphcdn.io/feedback

[hcentelles]

Oh, it seems like I’ll have to wait for that, at least for batch queries support.

I’ll try to keep myself updated on your changelog.