Webiny Architecture - API

API Architecture Graph

Webiny Serverless CMS - Architecture - API

The API architecture represents all of the cloud resources needed to host HTTP APIs, be it a simple REST API consisting of a couple of REST routes, or a fully fledged GraphQL API, consisting of many federated Federated GraphQL services and served via a single endpoint (URL) via the Apollo GraphQL gateway.


  • A - CloudFront web distribution
  • B - APIGateway
  • C - Apollo Gateway service
  • D - Federated GraphQL services
  • E - DB Proxy service
  • F - Database

Request Flow

  1. Client makes a POST request to the /graphql endpoint.

    Webiny also supports REST services. In that case the endpoint path will be different. For REST endpoints the request is routed directly to the function of a federated GraphQL service, without the (C) Apollo Gateway in between.

  2. All requests first land on the (A) CloudFront web distribution, which has the (B) API Gateway set as one of the origins.

  3. The (B) APIGateway invokes the (C) Apollo Gateway service

    • The (C) Apollo Gateway service is responsible for combining multiple (D) federated GraphQL services into a single GraphQL endpoint, using Apollo Federation.
    • Webiny comes with a GraphQL Playground built-in. Point your browser to the {your-domain}/graphql to view the playground and explore the full schema.
  4. When a POST request lands on the (C) Apollo Gateway service, the service internally invokes the required (D) federated GraphQL services.

  5. Every (D) federated GraphQL service internally processes and in some cases fetches the data from the database.

    • For all database-related tasks, Webiny heavily relies on a library called Commodo.
  6. In cases where Commodo is using MongoDB as the database, the queries are not sent directly to the database, but rather proxied through (E) DB Proxy service.

    Learn more about the DB Proxy in this blog post.

Last updated on by Adrian Smijulj