Apollo Server is the best way to build a production ready GraphQL server. It is designed from day one to make it easy to connect data from your backend(s) to a well designed schema ready for clients to use! Apollo Server is designed to work with every major Node HTTP servers such as Express, Hapi, and Koa, as well as serverless environments like AWS Lambda.
This documentation aims to provide a complete guide of how to build a GraphQL server by providing easy-to-understand overviews, in-depth guides and comprehensive best-practices.
The documentation is organized with basic concepts and design decisions first and more advanced topics later on.
* Intro as documentation for how to write a GraphQL server
* what a gql server is
* covers GraphQL concepts in server context, will not explain concepts in depth or the theory behind them/
* why is GraphQL more effective on the server
* Each section will have prereqs to get the most out of it
The docs for Apollo Server are mainly written using the [Express integration](), but most of the examples work no matter what server library you use. The docs are broken into six distinct sections to make it easy to find your way around:
Apollo Server, and the rest of the Apollo ecosystem, give you a powerful set of tools to rapidly stand up a GraphQL API on top of your existing, or new, backends. It does this by focusing on a schema-first approach where you build your schema with a concise, declarative syntax, and fill in the logic with data fetching resolver functions. It is easy to get started with [one-step mocking]() while you fill out your data and build your UI. With powerful tools like [schema directives](), [tracing and cache control](), and [schema stitching](), you can build the service of your dreams without writing a line of code more than you need.
