FastQL

I was always pained by the small things when I used REST APIs. You need just that one thing for this mobile app screen? Ok, here's 100 things! Or, even worse, you need 2 things, and they're two separate API endpoints. I guess we should invest in making some really great loading spinners for this app... So I got hooked on building interfaces using GraphQL APIs. You get exactly what you need, nothing more, nothing less. You can include multiple queries in 1 API call. Great right? Then I put it in practice, and everything was great. It was just time to turn on the CDN...it's not nice to have my users in Europe waiting on my server in Oregon, and this content doesn't change that often. But nope, nothing really worked. POST? CDNs don't like POST. What happens when my data changes? How do I purge the caches? CDNs want you to just purge by URL...in GraphQL there's only 1 URL for every API call. So, we set out to solve this, and in the process we started realizing all the neat things you can do when your CDN understands what your client is asking for, and what your server is delivering. Automatically removing stale data, partial caching, etc. Anyways, I hope others find this useful!