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. Platform as a Service
  4. Platform As A Service
  5. Apollo vs Azure Websites

Apollo vs Azure Websites

OverviewDecisionsComparisonAlternatives

Overview

Azure Websites
Azure Websites
Stacks404
Followers404
Votes23
Apollo
Apollo
Stacks2.7K
Followers1.8K
Votes25

Apollo vs Azure Websites: What are the differences?

**Introduction:**
Apollo and Azure Websites are two popular platforms used for hosting websites. Both offer a range of features and services, but they have distinct differences that set them apart.

**1. Scalability:**
One key difference between Apollo and Azure Websites is scalability. Apollo is built on a serverless architecture, making it easy to scale resources up or down based on demand, while Azure Websites offer scalable options but require more manual configuration and management.

**2. Pricing Model:**
Another significant difference is the pricing model. Apollo follows a pay-as-you-go pricing model, where you pay only for the resources you use, while Azure Websites offer various pricing tiers with fixed costs based on the resources allocated.

**3. Deployment Options:**
Apollo provides seamless integration with Git for continuous deployment, allowing for easy updates and rollbacks, while Azure Websites also support Git deployment but may require additional setup and configurations.

**4. Performance Monitoring:**
In terms of performance monitoring, Apollo offers built-in tools and analytics to monitor website performance and track metrics, whereas Azure Websites provide monitoring tools but may require additional third-party services for advanced analytics.

**5. Security Features:**
When it comes to security features, Apollo includes robust security measures by default, such as DDoS protection and SSL encryption, whereas Azure Websites offer security options but may require additional configurations for enhanced protection.

**6. Integration Capabilities:**
Apollo has seamless integration with other Apollo services and GraphQL APIs, providing a cohesive development experience, while Azure Websites offer integration with various Azure services but may require additional setup for some integrations.

In Summary, Apollo and Azure Websites differ in scalability, pricing, deployment options, performance monitoring, security features, and integration capabilities, offering users a range of choices based on their specific needs and preferences.

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 Azure Websites, Apollo

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
Raj
Raj

CTO & Founder at Novvum

Oct 5, 2020

Review

Hey Brian, it's hard to pick a best tool for any situation, however, there are tools that offer advantages dependent on use case.

Server Side

If you're looking to quickly generate a GraphQL API, you can use a Graphql As A Service like FaunaDB, Slash Graphql, or 8base.

If you want something more advanced on the server side: Prisma with Postgres, Nexus, & Apollo Server (js) is a great stack to try out. Examples here

Check out TypeORM and TypeGraphQL too

If you're have some existing data on Postgres, PostGraphile or Hasura are your best bet!

If you are using a lot of AWS services, check out Amplify and AppSync. Tutorial here

On the client side:

Check out Gatsby! Graphql is already configured and used to query static or remote information at build time. It's a great way to get your feet wet!

Apollo Client is often the choice for more advanced use cases. But URLQL and gqless are some pretty good alternatives too!

Hope this helps! 👍

295 views295
Comments

Detailed Comparison

Azure Websites
Azure Websites
Apollo
Apollo

Azure Websites is a fully managed Platform-as-a-Service (PaaS) that enables you to build, deploy and scale enterprise-grade web Apps in seconds. Focus on your application code, and let Azure take care of the infrastructure to scale and securely run it for you.

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.

.NET, Java, PHP, Node.js, Python;Built-in AutoScale and Load Balancing;High Availability with Auto-Patching;Continuous Deployment with Git, TFS, GitHub;SQL Databases, MySQL, DocumentDB, Search, MongoDB;WordPress, Umbraco, Joomla, Drupal
-
Statistics
Stacks
404
Stacks
2.7K
Followers
404
Followers
1.8K
Votes
23
Votes
25
Pros & Cons
Pros
  • 17
    Ease of deployment
  • 6
    Free plans for students
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 Azure Websites, 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.

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.

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.

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.

Render

Render

Render is a unified platform to build and run all your apps and websites with free SSL, a global CDN, private networks and auto deploys from Git.

Hasura

Hasura

An open source GraphQL engine that deploys instant, realtime GraphQL APIs on any Postgres database.

Cloud 66

Cloud 66

Cloud 66 gives you everything you need to build, deploy and maintain your applications on any cloud, without the headache of dealing with "server stuff". Frameworks: Ruby on Rails, Node.js, Jamstack, Laravel, GoLang, and more.

Jelastic

Jelastic

Jelastic is a Multi-Cloud DevOps PaaS for ISVs, telcos, service providers and enterprises needing to speed up development, reduce cost of IT infrastructure, improve uptime and security.

Dokku

Dokku

It is an extensible, open source Platform as a Service that runs on a single server of your choice. It helps you build and manage the lifecycle of applications from building to scaling.

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