Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Apollo
Apollo

821
581
+ 1
9
Parse-Server
Parse-Server

99
99
+ 1
19
Add tool

Apollo vs Parse-Server: What are the differences?

Developers describe Apollo as "GraphQL server for Express, Connect, Hapi, Koa and more". Build a universal GraphQL API on top of your existing REST APIs, so you can ship new application features fast without waiting on backend changes. On the other hand, Parse-Server is detailed as "Parse-compatible API server module for Node/Express". A Parse.com API compatible router package for Express. Read the announcement blog post here: http://blog.parse.com/announcements/introducing-parse-server-and-the-database-migration-tool/. Read the migration guide here: https://parse.com/docs/server/guide#migrating.

Apollo and Parse-Server are primarily classified as "Platform as a Service" and "Platform as a Service" tools respectively.

"From the creators of Meteor" is the top reason why over 8 developers like Apollo, while over 7 developers mention "Open Source" as the leading cause for choosing Parse-Server.

Apollo and Parse-Server are both open source tools. It seems that Parse-Server with 16.5K GitHub stars and 4.16K forks on GitHub has more adoption than Apollo with 7.4K GitHub stars and 911 GitHub forks.

According to the StackShare community, Apollo has a broader approval, being mentioned in 123 company stacks & 121 developers stacks; compared to Parse-Server, which is listed in 9 company stacks and 12 developer stacks.

What is Apollo?

Build a universal GraphQL API on top of your existing REST APIs, so you can ship new application features fast without waiting on backend changes.

What is Parse-Server?

A Parse.com API compatible router package for Express. Read the announcement blog post here: http://blog.parse.com/announcements/introducing-parse-server-and-the-database-migration-tool/. Read the migration guide here: https://parse.com/docs/server/guide#migrating
Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Why do developers choose Apollo?
Why do developers choose Parse-Server?

Sign up to add, upvote and see more prosMake informed product decisions

    Be the first to leave a con
    What companies use Apollo?
    What companies use Parse-Server?

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Apollo?
    What tools integrate with Parse-Server?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    What are some alternatives to Apollo and Parse-Server?
    Helios
    Helios is a Docker orchestration platform for deploying and managing containers across an entire fleet of servers. Helios provides a HTTP API as well as a command-line client to interact with servers running your containers.
    GraphQL
    GraphQL is a data query language and runtime designed and used at Facebook to request and deliver data to mobile and web apps since 2012.
    Python
    Python is a general purpose programming language created by Guido Van Rossum. Python is most praised for its elegant syntax and readable code, if you are just beginning your programming career python suits you best.
    Heroku
    Heroku is a cloud application platform – a new way of building and deploying web apps. Heroku lets app developers spend 100% of their time on their application code, not managing servers, deployment, ongoing operations, or scaling.
    Google App Engine
    Google has a reputation for highly reliable, high performance infrastructure. With App Engine you can take advantage of the 10 years of knowledge Google has in running massively scalable, performance driven systems. App Engine applications are easy to build, easy to maintain, and easy to scale as your traffic and data storage needs grow.
    See all alternatives
    Decisions about Apollo and Parse-Server
    Russel Werner
    Russel Werner
    Lead Engineer at StackShare · | 17 upvotes · 204.6K views
    atStackShareStackShare
    Redis
    Redis
    CircleCI
    CircleCI
    Webpack
    Webpack
    Amazon CloudFront
    Amazon CloudFront
    Amazon S3
    Amazon S3
    GitHub
    GitHub
    Heroku
    Heroku
    Rails
    Rails
    Node.js
    Node.js
    Apollo
    Apollo
    Glamorous
    Glamorous
    React
    React
    #StackDecisionsLaunch
    #SSR
    #Microservices
    #FrontEndRepoSplit

    StackShare Feed is built entirely with React, Glamorous, and Apollo. One of our objectives with the public launch of the Feed was to enable a Server-side rendered (SSR) experience for our organic search traffic. When you visit the StackShare Feed, and you aren't logged in, you are delivered the Trending feed experience. We use an in-house Node.js rendering microservice to generate this HTML. This microservice needs to run and serve requests independent of our Rails web app. Up until recently, we had a mono-repo with our Rails and React code living happily together and all served from the same web process. In order to deploy our SSR app into a Heroku environment, we needed to split out our front-end application into a separate repo in GitHub. The driving factor in this decision was mostly due to limitations imposed by Heroku specifically with how processes can't communicate with each other. A new SSR app was created in Heroku and linked directly to the frontend repo so it stays in-sync with changes.

    Related to this, we need a way to "deploy" our frontend changes to various server environments without building & releasing the entire Ruby application. We built a hybrid Amazon S3 Amazon CloudFront solution to host our Webpack bundles. A new CircleCI script builds the bundles and uploads them to S3. The final step in our rollout is to update some keys in Redis so our Rails app knows which bundles to serve. The result of these efforts were significant. Our frontend team now moves independently of our backend team, our build & release process takes only a few minutes, we are now using an edge CDN to serve JS assets, and we have pre-rendered React pages!

    #StackDecisionsLaunch #SSR #Microservices #FrontEndRepoSplit

    See more
    Munkhtegsh Munkhbat
    Munkhtegsh Munkhbat
    Software Engineer Consultant at LoanSnap · | 9 upvotes · 19.5K views
    GraphQL
    GraphQL
    Apollo
    Apollo
    React
    React
    Heroku
    Heroku
    styled-components
    styled-components
    PostgreSQL
    PostgreSQL
    Prisma
    Prisma
    graphql-yoga
    graphql-yoga
    #Backend
    #Frontend

    In my last side project, I built a web posting application that has similar features as Facebook and hosted on Heroku. The user can register an account, create posts, upload images and share with others. I took an advantage of graphql-subscriptions to handle realtime notifications in the comments section. Currently, I'm at the last stage of styling and building layouts.

    For the #Backend I used graphql-yoga, Prisma, GraphQL with PostgreSQL database. For the #FrontEnd: React, styled-components with Apollo. The app is hosted on Heroku.

    See more
    Interest over time
    Reviews of Apollo and Parse-Server
    Avatar of daxeel
    Prattle
    Review ofParse-ServerParse-Server

    Parse-server can be set up in any cloud with few commands. Easy to use and manage best Platform.

    How developers use Apollo and Parse-Server
    Avatar of jasonmjohnson
    jasonmjohnson uses ApolloApollo

    Apollo will be used to make requests to the GraphQL server and manage data handling/caching of responses.

    Avatar of Tanguy Cazalets
    Tanguy Cazalets uses ApolloApollo

    Implémentation de GraphQL

    Avatar of Ed Sweeney
    Ed Sweeney uses Parse-ServerParse-Server

    easy programming model

    How much does Apollo cost?
    How much does Parse-Server cost?
    Pricing unavailable
    Pricing unavailable
    News about Parse-Server
    More news