October 03, 2019
That’s nearly impossible today.
According to its creator GraphQL is expected to become ubiquitous in 2020-2021. Today is in the phase of being accepted by the large companies.
The official GraphQL page lists only a handful of services ready to build upon. Of them a few are complete solutions — backends as a service — and of them a few are production ready.
What’s left is Apollo, GraphCMS and AWS AppSync.
Before checking them let’s see how an ideal GraphQL API backend should look like.
An ideal service would offer the following features:
In other words:
That would mean rapid prototyping.
Both of them support all requirements except 1.) the visual scheme designer.
In Apollo all tasks imply (mostly) manual work. In AWS AppSync + Amplify everything is automated.
No wonder. Their description and distinctive features are put pretty clear on GraphQL.org.
Apollo Engine: A service for monitoring the performance and usage of your GraphQL backend.
AWS AppSync: Fully managed GraphQL service with realtime subscriptions, offline programming & synchronization, and enterprise security features as well as fine grained authorization controls.
One has to choose AWS AppSync then, or dive deep into Apollo to find hidden gems unsurfaced during this quick research.
However in our collective mindset AWS is for large scale production apps and enterprise use not for rapid prototyping. All plans are paid and every operation is billed.
GraphCMS to the rescue?
From the list of developer friendly headless CMS services on JAMStack — including Contentful, GraphCMS, Sanity, TakeShape, Prismic, Kentico — only a few experiences worth it.
Setting up an account and trying to get a GraphQL endpoint on a free plan was tedious or impossible in many times:
Wait for the Headless CMS scene to take off.
Otherwise, if needed right now, go with AWS. All services can be used for free for a year.
Is AWS expensive? It’s a Tier 1 service. Probably all other Headless CMS providers on upper tiers are building upon its infrastructure — increasing the bill.
To React with best practices. Written by @metamn.