I’ve been using Apollo GraphOS across several mobile and web projects. On the mobile side, I’ve integrated it with React Native and Flutter. For web applications, the usage has been primarily within React-based projects. My development environment typically includes CI/CD pipelines, modular architecture, and cloud deployments, and Apollo GraphOS fits smoothly into this ecosystem. It helps streamline the way we manage our GraphQL layer and aligns well with modern frontend workflows which is a very nice to have experience
Reviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
12 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Access data seamlessly with robust community support without current improvement needs
What is our primary use case?
How has it helped my organization?
Apollo GraphOS has significantly enhanced both the developer experience and product delivery timelines. By offering a centralised approach to managing GraphQL schemas and services, it has helped reduce overhead and improved collaboration between frontend and backend teams. The ability to monitor query performance and usage metrics directly has been particularly useful for optimizing API interactions. It also adds a level of confidence to schema changes, thanks to built-in checks and insights, which contributes to more robust deployments.
What is most valuable?
One of the standout features is the intuitive support for mutations and the flexibility they provide. They make state updates seamless and reduce the boilerplate often associated with RESTful services. I also value the Schema Registry and Federation capabilities, which enable us to build scalable, modular APIs while avoiding tight coupling. Community support and documentation have also been excellent, helping us get up to speed quickly and troubleshoot when needed. Overall, the ability to efficiently fetch only the data needed with minimal friction makes development much faster and cleaner.
What needs improvement?
So far, I could say that Apollo GraphOS is quite comprehensive, there’s room for improvement in schema collaboration tools, especially in large teams where multiple developers are working on overlapping parts of the API. More granular access control and role-based visibility within the platform would help enterprise teams better manage who can change what. Enhanced support for real-time use cases (e.g., subscriptions at scale) could also take it to the next level and give a better developer experience
These might also be beneficial to have a more in-depth analytics around client usage and field-level insights to drive better decisions around deprecation or optimization.
For how long have I used the solution?
I have been using Apollo GraphOS for around three to four years now.
What do I think about the stability of the solution?
I have not had any issues with stability. There have been no instances of it breaking down.
What do I think about the scalability of the solution?
Apollo GraphOS is quite scalable. I love the versioning that comes with the Sandbox, which helps track changes over time.
How are customer service and support?
I have never had to contact their support team for any reason. The documentation has been my go-to resource.
How would you rate customer service and support?
Positive
How was the initial setup?
The initial setup is quite easy, as it is designed to easily toggle between development and production.
What other advice do I have?
I rate Apollo GraphOS a seven out of ten. I feel like it's a great product, and it deserves this rating, and it could even be an eight.
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other
Efficiently filters API data though experiences slower performance with larger projects
What is our primary use case?
I primarily use Apollo GraphQL to work with APIs in conjunction with Node.js. When I make API calls, I receive a lot of information, but I only need specific details like names, emails, and photos. Using Apollo GraphQL, I can filter out unnecessary information, which improves performance. I have deployed it on my GitHub account.
What is most valuable?
The most valuable features of Apollo GraphQL are its security and authentication process. These roles are crucial, especially when working with APIs. Its ability to filter and streamline API responses for performance efficiency is also highly appreciated.
What needs improvement?
I would like to see better performance in larger projects. When dealing with large amounts of data, it can become slow, causing users to potentially abandon the application. Improving performance and ensuring the app runs smoothly would enhance user experience. Stability issues, where it sometimes breaks down, need to be addressed as well.
For how long have I used the solution?
I have been using Apollo GraphQL for about three years.
What do I think about the stability of the solution?
While Apollo GraphQL is stable 70% of the time, it does have breakdowns. Sometimes it does not connect, and given that they are continuously working on it, these issues occasionally arise.
What do I think about the scalability of the solution?
Apollo GraphQL's performance depends on API requests, updates, and deletions. However, scalability can be a concern as network issues sometimes cause it to break down.
How are customer service and support?
I have not contacted Apollo GraphQL's support team directly. I usually get help from friends and developers who are familiar with it.
How would you rate customer service and support?
Neutral
How was the initial setup?
The setup process is not very easy but not too difficult either. It is more of an intermediate level process.
What's my experience with pricing, setup cost, and licensing?
I am not sensitive to nor very knowledgeable about the pricing and setup cost.
What other advice do I have?
From one to ten, I would rate Apollo GraphQL six or six point five. Despite its benefits, it can sometimes break down badly, and the need for continuous improvements might involve handling heavy loads, especially for smaller to medium apps. I rate the overall solution at 6.5.
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other
Best Api gateway
What do you like best about the product?
Apollographql.com is easy to use and provide a platform for easy implementation of apis, learning about them, and smooth integration with our codes. It also provide a rich documentation for users and customer support as well if needed.
What do you dislike about the product?
Due to its rich functionality, it might confuse new developers, and for small projects looking for flexibility, it might not be best option.
What problems is the product solving and how is that benefiting you?
It is helping in simplifing the complexity of data being fetched by allowing us to fetch just the data we need, not less not more. Also, one more benefit is that it allows using multiple sources at once for our data.
Graphql - AWS Appsync and DynamoDb
What do you like best about the product?
Apollo GraphQL has been instrumental in our application performance solution app development, providing a streamlined way to manage data flow between client and server. Apollo enabled efficient data fetching, caching, and state management, integrating seamlessly with front-end frameworks. Integration with AWS Cognito helped us to manage platform and made implementation easier.
What do you dislike about the product?
GraphQL requires developers to define a comprehensive schema upfront, including types, queries, mutations, and relationships. This can be challenging to plan and maintain,
What problems is the product solving and how is that benefiting you?
Using GraphQL with DynamoDB provides a powerful combination, especially for applications that require flexible, real-time data access and are built on serverless or NoSQL architectures.
Apollo is one stop stack for GraphQL use cases
What do you like best about the product?
It is a mature product, supports graphql server, supports building Gateway, supergraphs and subgraphs with ease.
It has client side products for various frameworks.
It has client side products for various frameworks.
What do you dislike about the product?
Overall it is good but it has a steep learning curve.
What problems is the product solving and how is that benefiting you?
Building GraphQL backend servers, and consuming data on client side.
Great for Developers
What do you like best about the product?
Its has user friendly graphic interface easy to understand, provide real time updates and dev tools.
What do you dislike about the product?
No, I am using this tool. but didn't find any dislike
What problems is the product solving and how is that benefiting you?
It helps me to work with complex api's and with this i can handle my apps data very easily. Its real time featureis very good it updates automatically when something change in data. I loved this it solves all my problems.
The best GraphQL Platform, hands down
What do you like best about the product?
- Easy to implement.
- Extremely robust feature set.
- Provides both client and server solutions, making integration simpler.
- Self-documenting APIs.
- Strong developer documentation.
- Extremely robust feature set.
- Provides both client and server solutions, making integration simpler.
- Self-documenting APIs.
- Strong developer documentation.
What do you dislike about the product?
- Limited to using NodeJS as a runtime, which limits platform compatibility somewhat.
What problems is the product solving and how is that benefiting you?
It allows us to provide a fully-featured GraphQL API with support for subscriptions, while also giving us a GraphQL client with built-in state management and caching mechanisms.
Game changer for developers
What do you like best about the product?
The documentation is easy to understand and very simple to learn. Easily handle local and remote data
What do you dislike about the product?
Till now i dont find any dislike about this product.
What problems is the product solving and how is that benefiting you?
Its makes easy to handle and fetch data from api's. we can request exactly what we need. It helps me to get real time data very easily. It works very well with Reactjs and Vuejs.
One of the best GraphQL tool
What do you like best about the product?
very easy to use graphql client, have a great microservice potential for graphql. also it integrate seamlesly in reactjs project.
What do you dislike about the product?
even after using it in more than 3 projects, could not find any dislike about it.
What problems is the product solving and how is that benefiting you?
it help to get data via graphql query across all our frontend app, its being the quite powerful and user friendly.
Dynamic API for all the needs
What do you like best about the product?
It has the excellent ability to cater to the required parameters irrespective of vintage static Rest API architecture.
What do you dislike about the product?
Complex data Structures sometimes becoming challenging if not properly handled.
What problems is the product solving and how is that benefiting you?
Multiple API handles are reduced with GraphQL
showing 1 - 10