That's nearly impossible today.

GraphQL is young

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.

• Graphcool - is self hosted
• Reindex - looks empty
• Scaphold - closed down
• Tipe - is in beta
• Hasura - has no pricing plans

What's left is Apollo, GraphCMS and AWS AppSync.

Before checking them let's see how an ideal GraphQL API backend should look like.

The ideal GraphQL API service

An ideal service would offer the following features:

1. Visual Schema designer
2. Automatic database generation based on the schema
3. Automatic resolver generation
4. Automatic lambda function generation for the resolvers
5. Automatic Type / Schema code generation and sync for clients

In other words:

• One should be able to visually design the data structure
• From that design all else — possible — is automatically generated: database tables, resolvers, lambda functions, schema, types, boilerplate client code
• On client side, during development, when the schema is modified it is automatically synced with the backend.

That would mean rapid prototyping.

Apollo and AWS AppSync

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?

Headless CMS is young (and not enough)

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:

• Contentful - No GraphQL on the free plan
• GraphCMS - Except 5.) Automatic code generation and sync — it offers all other features. However these features seems to be undocumented and very fragile.
• Sanity - A strange, download first approach. Skipped for now.
• TakeShape - The GraphQL endpoint works out of the box. Worth experiencing with it further.
• Prismic - GraphQL support has to be asked for / enabled manually by the support team. Worth experiencing with it further.
• WPGraphQL - Works perfect however is tailored to the WordPress data structure. It can be extended of course but WordPress is a specific, not a general purpose CMS.

Conclusion

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.

Resources

• Is GraphQL Moving Toward Ubiquity?
• GraphQL Services
• Apollo Introduction
• A list of developer friendly headless CMS services on JAMStack