Architecture, Hosting, and Infrastructure

Where is GraphCMS being hosted?

Our servers, Amazon’s AWS and Google Cloud, are deployed on three continents for best performance and reliability (Europe/EU (Ireland, Germany), US East (Virginia), US West (Oregon), Asia (Japan)).

Which databases does GraphCMS use?

AWS Aurora MySQL is used for the Project APIs of your projects and Google PostgreSQL for your Management API.

Is the GraphCMS architecture horizontally scalable?

Yes, we have a modern and scalable architecture based on Kubernetes and scalable databases such as AWS Aurora and Postgres.

Is GraphCMS multi-tenant?

Yes, this is possible with cloning. We support hosting in four regions out of the box (Europe/EU (Ireland, Germany), US East (Virginia), US West (Oregon), Asia (Japan)). More regions are available with dedicated infrastructure.

Is the storage size or the number of entries and records in a GraphCMS project limited?

There are no limits on storage or project entries and records.

What are the GraphCMS latency metrics?

Latency depends on your location, the location of your users, and the complexity of your GraphQL queries. We aim for a latency of maximum 70-100 ms for requests.

How are media assets hosted and delivered with GraphCMS?

Media assets are delivered via our asset management provider Filestack and the content distribution network Fastly (CDN).

Where are my application files (e.g. html and javascript) hosted?

Your application files are entirely in your control. The GraphCMS API is used for delivering content, compatible services like Netlify or Zeit are used for hosting the application files.

What is your GraphQL caching strategy?

GraphCMS uses the default by id apollo caching strategy for the majority of the webapp. The exception being content queries which can change so dynamically that Urql is used to handle/cache them and invalidate everything when the content data changes.