An easier way to manage the data sources powering your GraphQL server.
GrAMPS (short for GraphQL Apollo Microservice Pattern Server) is middleware designed for apollo-server-express that allows independent data sources — a schema, resolvers, and data access model — to be composed into a single GraphQL schema, while keeping the code within each data source isolated, independently testable, and completely decoupled from the rest of your application.
GrAMPS is an attempt to create a standard for organizing GraphQL data source repositories, which allows for multiple data sources to be composed together in a plugin-like architecture.
The architecture of GrAMPS data sources was inspired by @helfer, who suggested models and connectors as abstractions when designing GraphQL servers. GrAMPS expands on the original concept and provides a standard that makes separate codebases interoperable.
The ability to combine independently managed data sources into a single GraphQL server is a core requirement for IBM Cloud’s microservice architecture. We have dozens of teams who expose data, so a single codebase with all GraphQL data sources inside was not an option; we needed a way to give each team control of their data while still maintaining the ability to simplify our data layer.
GrAMPS solves this problem by allowing each data source to be an independent repository/package that can be composed together into a single GraphQL server.
GQL_DATA_SOURCESor in the
--data-source-dirargument to the CLI command
graphqlExpressto start the server
GrAMPS was born at IBM Cloud to solve the problem of maintaining a single GraphQL endpoint in a µ-service architecture where data sources are owned by dozens of teams.
We’re releasing it under the MIT license because we ❤️ the developer community.