Apollo is the industry-standard GraphQL implementation, providing the data graph layer that connects modern apps to the cloud.
REST APIs are not a good fit for modern apps because they require large amounts of hard-to-manage data fetching code. With Apollo, components simply declare their data requirements using GraphQL and Apollo gets the right data to the right place – with strong end-to-end typing that prevents bugs and boosts productivity.
Apollo presents all of your organization’s data sources as one connected data graph that’s always up to date. You can easily browse everything that’s available, join data across multiple sources, and get the results in the shape you need and on any platform.
Apollo is a great fit with microservice architectures and modern UI frameworks like React. It serves as an abstraction layer that decouples services and apps so that each can be developed independently of the other, in any language and on any platform.
Adding a data graph layer to your stack lets your team build new features – and bring your app to new platforms – in a fraction of the time. App developers can delete thousands of lines of tedious boilerplate code, move fast without waiting on back-end teams, and more easily keep features consistent across web and mobile platforms.
If you’re using Apollo Android, the chances are that you are using a schema.json file: an introspection schema. While introspection schemas work well, GraphQL has SDL (Schema Definition Language), which is another, more concise, way to describe a schema. The excellent news is that Apollo Android supports SDL! Read below to learn more about SDL and how to enable […]
One of the most common use cases front-end developers face is re-render the UI after executing a mutation and changing something in the backend. To solve this problem, a lot of developers like to use the refetchQueries API. For example, if I wanted to add a todo to a list of todos, I might pass […]
Most organizations’ adventures with GraphQL start with one team looking for a way to solve one of the most significant frontend development problems in a microservice architecture: how to get all the data your app needs without making a million and one service calls. For a frontend engineer, that promise of getting all the data […]