Get Advice Icon

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

Aerobatic
Aerobatic

3
12
+ 1
2
Apollo
Apollo

784
559
+ 1
9
Add tool

Aerobatic vs Apollo: What are the differences?

What is Aerobatic? Smart Hosting for Single Page Apps. In a nutshell, it's a platform as a service (PaaS) for HTML5 web apps. You could think of it as Heroku for the front-end. It provides a streamlined developer workflow and a suite of cloud-based smart hosting modules that are highly complementary to your custom app code running in the browser.

What is Apollo? 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.

Aerobatic and Apollo can be primarily classified as "Platform as a Service" tools.

Apollo is an open source tool with 7.53K GitHub stars and 935 GitHub forks. Here's a link to Apollo's open source repository on GitHub.

- No public GitHub repository available -

What is Aerobatic?

In a nutshell, it's a platform as a service (PaaS) for HTML5 web apps. You could think of it as Heroku for the front-end. It provides a streamlined developer workflow and a suite of cloud-based smart hosting modules that are highly complementary to your custom app code running in the browser.

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.
Get Advice Icon

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

Why do developers choose Aerobatic?
Why do developers choose Apollo?
    Be the first to leave a con
      Be the first to leave a con
      What companies use Aerobatic?
      What companies use Apollo?
        No companies found

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

        What tools integrate with Aerobatic?
        What tools integrate with Apollo?

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

        What are some alternatives to Aerobatic and Apollo?
        Netlify
        Netlify is smart enough to process your site and make sure all assets gets optimized and served with perfect caching-headers from a cookie-less domain. We make sure your HTML is served straight from our CDN edge nodes without any round-trip to our backend servers and are the only ones to give you instant cache invalidation when you push a new deploy. Netlify is also the only static hosting service with integrated continuous deployment.
        BitBalloon
        BitBalloon deploys static sites from development to production in one step. Sites are automatically compressed, cached and pushed to a CDN. Any forms on the site will automatically work. BitBalloon is 100% programmable, everything from deployment to form handling can be controlled through the API. White label reseller options are available for using BitBalloon as a site publishing engine inside 3rd party authoring tools.
        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.
        AWS Elastic Beanstalk
        Once you upload your application, Elastic Beanstalk automatically handles the deployment details of capacity provisioning, load balancing, auto-scaling, and application health monitoring.
        See all alternatives
        Decisions about Aerobatic and Apollo
        Russel Werner
        Russel Werner
        Lead Engineer at StackShare · | 15 upvotes · 166.9K 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
        #FrontEndRepoSplit
        #Microservices
        #SSR
        #StackDecisionsLaunch

        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 · 12.9K views
        GraphQL
        GraphQL
        Apollo
        Apollo
        React
        React
        Heroku
        Heroku
        styled-components
        styled-components
        PostgreSQL
        PostgreSQL
        Prisma
        Prisma
        graphql-yoga
        graphql-yoga
        #Frontend
        #Backend

        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 Aerobatic and Apollo
        No reviews found
        How developers use Aerobatic and Apollo
        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

        How much does Aerobatic cost?
        How much does Apollo cost?
        Pricing unavailable
        Pricing unavailable
        News about Aerobatic
        More news