# GraphQL over REST with Node, Heroku, and Apollo Engine

DevFeed: [GraphQL over REST with Node, Heroku, and Apollo Engine](<https://devfeed.tech/articles/graphql-over-rest-with-node-heroku-and-apollo-engine-23333.md>)

Original publisher: [Read original article](<https://www.apollographql.com/blog/graphql-over-rest-with-node-heroku-and-apollo-engine-fb8581f8d77f>)

Author: Sashko Stubailo

Published: 2018-03-14T21:21:00Z

Content type: tutorial

Language: en

Sources: [Apollo Blog](<https://devfeed.tech/sources/apollo-blog.md>)

Topics: [GraphQL](<https://devfeed.tech/topics/graphql.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>), [apollo-server](<https://devfeed.tech/topics/apollo-server.md>), [Heroku](<https://devfeed.tech/topics/heroku.md>), [Amazon API Gateway](<https://devfeed.tech/topics/amazon-api-gateway.md>), [Caching](<https://devfeed.tech/topics/caching.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [api-gateway](<https://devfeed.tech/tags/api-gateway.md>), [apollo](<https://devfeed.tech/tags/apollo.md>), [caching](<https://devfeed.tech/tags/caching.md>), [community](<https://devfeed.tech/tags/community.md>), [graphql](<https://devfeed.tech/tags/graphql.md>), [heroku](<https://devfeed.tech/tags/heroku.md>), [node](<https://devfeed.tech/tags/node.md>), [performance-monitoring](<https://devfeed.tech/tags/performance-monitoring.md>), [rest](<https://devfeed.tech/tags/rest.md>), [tutorial](<https://devfeed.tech/tags/tutorial.md>)

## AI overview

This tutorial explains how to wrap existing REST endpoints in a GraphQL API using Node and Apollo Server. It also presents deployment on Heroku with Apollo Engine, covering GraphQL schema design, resolvers, caching, and performance monitoring.

## Source excerpt

Wrapping your REST endpoints in GraphQL is a quick way to make it easier to use the data you have in your existing backends. In just a few hours, you can implement a thin translation layer using Node and Apollo Server and start getting the main benefits of having a GraphQL API without having to dive in to the backend implementation. Why wrap your REST API with GraphQL?