StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. Cloud Hosting
  4. Cloud Hosting
  5. Amazon EC2 vs Apollo

Amazon EC2 vs Apollo

OverviewDecisionsComparisonAlternatives

Overview

Amazon EC2
Amazon EC2
Stacks48.6K
Followers36.0K
Votes2.5K
Apollo
Apollo
Stacks2.7K
Followers1.8K
Votes25

Amazon EC2 vs Apollo: What are the differences?

Introduction

This markdown code compares the key differences between Amazon EC2 and Apollo. Amazon EC2 and Apollo are both cloud computing platforms, but they have some distinct differences that set them apart. The following paragraphs highlight six key differences between these platforms.

  1. Provisioning: Amazon EC2 is a Infrastructure as a Service (IaaS) platform that allows users to provision virtual servers in the cloud. Users have full control over their virtual servers, including the choice of operating systems and configurations. On the other hand, Apollo is a Platform as a Service (PaaS) platform that focuses on application deployment and management. It abstracts away the underlying infrastructure and provides a simplified deployment experience for developers.

  2. Server Types: Amazon EC2 offers a wide variety of server types to meet specific workload requirements, such as general-purpose, memory-optimized, and GPU instances. It allows users to choose the appropriate server type based on their application needs. In contrast, Apollo provides a standardized server type for all applications. It simplifies the deployment process by offering a single server type optimized for most use cases.

  3. Scalability: Amazon EC2 allows users to scale their infrastructure up or down based on demand. Users can easily add or remove instances to match the workload requirements. It provides flexible scaling options, including manual scaling and auto scaling based on predefined metrics. On the other hand, Apollo is designed to automatically scale applications based on demand. It dynamically allocates resources to handle varying traffic loads, ensuring optimal performance without the need for manual intervention.

  4. Pricing: Amazon EC2 offers a pay-as-you-go pricing model. Users pay only for the resources they consume, such as instance hours and data transfer. The pricing is based on various factors, including instance type, region, and usage. In contrast, Apollo adopts a fixed pricing model. Users pay a flat fee for the resources allocated to their applications, regardless of the actual usage. This provides cost predictability, especially for applications with consistent resource requirements.

  5. Management: Amazon EC2 provides a comprehensive set of management tools, including APIs, command-line interface (CLI), and web console. Users can manage their instances, networking, and storage resources using these tools. It also integrates with other AWS services for enhanced functionality. Conversely, Apollo offers a simplified management experience. It handles most of the infrastructure management tasks automatically, allowing developers to focus more on application development rather than infrastructure maintenance.

  6. Service Ecosystem: Amazon EC2 is part of a larger ecosystem of cloud services provided by Amazon Web Services (AWS). It can be easily integrated with other AWS services such as Amazon S3 for object storage and Amazon RDS for managed databases. This offers a wide range of services and capabilities to enhance the overall application architecture. In contrast, Apollo is a standalone platform without a comparable ecosystem. It provides the necessary tools and resources for application deployment and scaling but lacks the additional services offered by AWS.

In summary, Amazon EC2 and Apollo differ in their provisioning models, server types, scalability approaches, pricing models, management tools, and service ecosystems. These differences make them suitable for different use cases and application requirements.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on Amazon EC2, Apollo

Craig
Craig

Principal Consultant at Rootwork InfoTech LLC

Jul 16, 2020

Decided

We first selected Google Cloud Platform about five years ago, because HIPAA compliance was significantly cheaper and easier on Google compared to AWS. We have stayed with Google Cloud because it provides an excellent command line tool for managing resources, and every resource has a well-designed, well-documented API. SDKs for most of these APIs are available for many popular languages. I have never worked with a cloud platform that's so amenable to automation. Google is also ahead of its competitors in Kubernetes support.

200k views200k
Comments
Jerome/Zen
Jerome/Zen

Software Engineer

Aug 2, 2020

Needs advice

DigitalOcean was where I began; its USD5/month is extremely competitive and the overall experience as highly user-friendly.

However, their offerings were lacking and integrating with other resources I had on AWS was getting more costly (due to transfer costs on AWS). Eventually I moved the entire project off DO's Droplets and onto AWS's EC2.

One may initially find the cost (w/o free tier) and interface of AWS daunting however with good planning you can achieve highly cost-efficient systems with savings plans, spot instances, etcetera.

Do not dive into AWS head-first! Seriously, don't. Stand back and read pricing documentation thoroughly. You can, not to the fault of AWS, easily go way overbudget. Your first action upon getting your AWS account should be to set up billing alarms for estimated and current bill totals.

264k views264k
Comments
Márton
Márton

CTO at Media4Care

Aug 31, 2020

Decided

We wanted to save as much time as possible when writing our back-end, therefore Apollo was out of the question, we went for an auto-generated API instead. Hasura looked good in the beginning, but we wanted to retain the ability to add a few manual resolvers and modifications to auto-generated ones, which ruled out Hasura. Postgraphile with its Plug-In architecture was the right choice for us, we never regretted it!

37.1k views37.1k
Comments

Detailed Comparison

Amazon EC2
Amazon EC2
Apollo
Apollo

It is a web service that provides resizable compute capacity in the cloud. It is designed to make web-scale computing easier for developers.

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.

Elastic – Amazon EC2 enables you to increase or decrease capacity within minutes, not hours or days. You can commission one, hundreds or even thousands of server instances simultaneously.;Completely Controlled – You have complete control of your instances. You have root access to each one, and you can interact with them as you would any machine.;Flexible – You have the choice of multiple instance types, operating systems, and software packages. Amazon EC2 allows you to select a configuration of memory, CPU, instance storage, and the boot partition size that is optimal for your choice of operating system and application.;Designed for use with other Amazon Web Services – Amazon EC2 works in conjunction with Amazon Simple Storage Service (Amazon S3), Amazon Relational Database Service (Amazon RDS), Amazon SimpleDB and Amazon Simple Queue Service (Amazon SQS) to provide a complete solution for computing, query processing and storage across a wide range of applications.;Reliable – Amazon EC2 offers a highly reliable environment where replacement instances can be rapidly and predictably commissioned. The Amazon EC2 Service Level Agreement commitment is 99.95% availability for each Amazon EC2 Region.;Secure – Amazon EC2 works in conjunction with Amazon VPC to provide security and robust networking functionality for your compute resources.;Inexpensive – Amazon EC2 passes on to you the financial benefits of Amazon’s scale. You pay a very low rate for the compute capacity you actually consume.;Easy to Start – Quickly get started with Amazon EC2 by visiting AWS Marketplace to choose preconfigured software on Amazon Machine Images (AMIs). You can quickly deploy this software to EC2 via 1-Click launch or with the EC2 console.
-
Statistics
Stacks
48.6K
Stacks
2.7K
Followers
36.0K
Followers
1.8K
Votes
2.5K
Votes
25
Pros & Cons
Pros
  • 647
    Quick and reliable cloud servers
  • 515
    Scalability
  • 393
    Easy management
  • 277
    Low cost
  • 271
    Auto-scaling
Cons
  • 14
    Ui could use a lot of work
  • 6
    High learning curve when compared to PaaS
  • 3
    Extremely poor CPU performance
Pros
  • 12
    From the creators of Meteor
  • 8
    Great documentation
  • 3
    Open source
  • 2
    Real time if use subscription
Cons
  • 1
    Increase in complexity of implementing (subscription)
  • 1
    File upload is not supported
Integrations
No integrations available
GraphQL
GraphQL

What are some alternatives to Amazon EC2, Apollo?

Heroku

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.

DigitalOcean

DigitalOcean

We take the complexities out of cloud hosting by offering blazing fast, on-demand SSD cloud servers, straightforward pricing, a simple API, and an easy-to-use control panel.

Clever Cloud

Clever Cloud

Clever Cloud is a polyglot cloud application platform. The service helps developers to build applications with many languages and services, with auto-scaling features and a true pay-as-you-go pricing model.

Microsoft Azure

Microsoft Azure

Azure is an open and flexible cloud platform that enables you to quickly build, deploy and manage applications across a global network of Microsoft-managed datacenters. You can build applications using any language, tool or framework. And you can integrate your public cloud applications with your existing IT environment.

Google App Engine

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.

Red Hat OpenShift

Red Hat OpenShift

OpenShift is Red Hat's Cloud Computing Platform as a Service (PaaS) offering. OpenShift is an application platform in the cloud where application developers and teams can build, test, deploy, and run their applications.

Google Compute Engine

Google Compute Engine

Google Compute Engine is a service that provides virtual machines that run on Google infrastructure. Google Compute Engine offers scale, performance, and value that allows you to easily launch large compute clusters on Google's infrastructure. There are no upfront investments and you can run up to thousands of virtual CPUs on a system that has been designed from the ground up to be fast, and to offer strong consistency of performance.

Linode

Linode

Get a server running in minutes with your choice of Linux distro, resources, and node location.

AWS Elastic Beanstalk

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.

Scaleway

Scaleway

European cloud computing company proposing a complete & simple public cloud ecosystem, bare-metal servers & private datacenter infrastructures.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase