Platform
Pricing

THE SUPERGRAPH

A new, powerful composition engine for your business and teams.

Explore the stack

REQUEST A DEMO

Tools for collaboration, observability, federation, and more.

See how we can help

APOLLO STUDIO

Develop

A central access point and hub for your team to stay up-to-date.

Deliver

Automatic tests for breaking changes in CI, and more.

Observe

Full insight into exactly how your graph is being used.

OPEN SOURCE

Apollo Client

Manage your full app's state and connect to queries seamlessly.

Apollo Federation

A single graph composed from multiple underlying services.

Tooling

Devtools and editor extensions for support directly in your workflow.

DEVELOPERS

Docs
GraphQL Tutorials
DevHub
Blog
Community
Events
YouTube

FEATURED EVENTS

GraphQL Summit
[Webinar On-Demand] 10 Best Practices for Schema Governance

ENTERPRISE

Explore tech talks, workshops, product updates & more.

Learn how to build and scale your graph.

Learn how Apollo's solutions and expertise can help you deliver innovation with a unified graph.

Learn how Apollo is transforming the way industry leaders build apps.

Read Apollo’s guide to scaling GraphQL in the Enterprise

ABOUT US

Leadership
Careers
Open Positions
Our Team

SUPPORT

Contact Sales
Get Help
Terms of Service
Privacy Policy
Contact Sales
Create Account

E-Book

Make the switch from REST to GraphQL

Learn best practices for schema design when migrating from REST to GraphQL


What You'll Learn

Why GraphQL is a better solution than REST for delivering new experiences

What pitfalls to avoid when migrating from REST to GraphQL

How to design your GraphQL schema the right way

The Journey from REST to GraphQL

Developers have rapidly adopted GraphQL since it open sourced in 2015. GraphQL focuses on creating APIs that are designed around how data will be consumed—improving the way developers build applications and enabling product teams to deliver new experiences faster. This differs from previous API technologies that focused on creating endpoints that were very data centric and not concerned with how data was going to be consumed.

How is GraphQL different from REST?
For developers, GraphQL reduces the amount of time they spend writing boilerplate, data-fetching code so they can focus on building features. Application performance also improves thanks to a reduced payload size and fewer roundtrips.

While many engineering teams rely on a REST architecture to deliver digital experiences for their users, REST does not easily scale to integrate new capabilities that organizations need to stay current and competitive. With GraphQL, client engineering teams have a more flexible way to fetch data and integrate additional capabilities into new and existing platforms as they pop up. This allows them to deliver more value to customers and drive business growth.

© 2022 Apollo Graph Inc.

Company

  • About Us
  • Careers
  • Open Positions
  • Team
  • Leadership
  • Interns