Need advice about which tool to choose?Ask the StackShare community!
AWS Elastic Beanstalk vs Azure Websites: What are the differences?
AWS Elastic Beanstalk: Quickly deploy and manage applications in the AWS cloud. Once you upload your application, Elastic Beanstalk automatically handles the deployment details of capacity provisioning, load balancing, auto-scaling, and application health monitoring; Azure Websites: Deploy and scale modern websites and web apps in seconds. 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.
AWS Elastic Beanstalk and Azure Websites can be primarily classified as "Platform as a Service" tools.
Some of the features offered by AWS Elastic Beanstalk are:
- Elastic Beanstalk is built using familiar software stacks such as the Apache HTTP Server for Node.js, PHP and Python, Passenger for Ruby, IIS 7.5 for .NET, and Apache Tomcat for Java
- There is no additional charge for Elastic Beanstalk - you pay only for the AWS resources needed to store and run your applications.
- Easy to begin – Elastic Beanstalk is a quick and simple way to deploy your application to AWS. You simply use the AWS Management Console, Git deployment, or an integrated development environment (IDE) such as Eclipse or Visual Studio to upload your application
On the other hand, Azure Websites provides the following key features:
- .NET, Java, PHP, Node.js, Python
- Built-in AutoScale and Load Balancing
- High Availability with Auto-Patching
"Integrates with other aws services" is the top reason why over 74 developers like AWS Elastic Beanstalk, while over 14 developers mention "Ease of deployment" as the leading cause for choosing Azure Websites.
According to the StackShare community, AWS Elastic Beanstalk has a broader approval, being mentioned in 374 company stacks & 118 developers stacks; compared to Azure Websites, which is listed in 73 company stacks and 36 developer stacks.
What is AWS Elastic Beanstalk?
What is Azure Websites?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose AWS Elastic Beanstalk?
Why do developers choose Azure Websites?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using AWS Elastic Beanstalk?
What are the cons of using Azure Websites?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with AWS Elastic Beanstalk?
What tools integrate with Azure Websites?
Sign up to get full access to all the tool integrationsMake informed product decisions
Gratify Commerce
When creating the web infrastructure for our start-up, I wanted to host our app on a PaaS to get started quickly.
A very popular one for Rails is Heroku, which I love for free hobby side projects, but never used professionally. On the other hand, I was very familiar with the AWS ecosystem, and since I was going to use some of its services anyways, I thought: why not go all in on it?
It turns out that Amazon offers a PaaS called AWS Elastic Beanstalk, which is basically like an “AWS Heroku”. It even comes with a similar command-line utility, called "eb”. While edge-case Rails problems are not as well documented as with Heroku, it was very satisfying to manage all our cloud services under the same AWS account. There are auto-scaling options for web and worker instances, which is a nice touch. Overall, it was reliable, and I would recommend it to anyone planning on heavily using AWS.
We initially started out with Heroku as our PaaS provider due to a desire to use it by our original developer for our Ruby on Rails application/website at the time. We were finding response times slow, it was painfully slow, sometimes taking 10 seconds to start loading the main page. Moving up to the next "compute" level was going to be very expensive.
We moved our site over to AWS Elastic Beanstalk , not only did response times on the site practically become instant, our cloud bill for the application was cut in half.
In database world we are currently using Amazon RDS for PostgreSQL also, we have both MariaDB and Microsoft SQL Server both hosted on Amazon RDS. The plan is to migrate to AWS Aurora Serverless for all 3 of those database systems.
Additional services we use for our public applications: AWS Lambda, Python, Redis, Memcached, AWS Elastic Load Balancing (ELB), Amazon Elasticsearch Service, Amazon ElastiCache
I use Gunicorn because does one thing - it’s a WSGI HTTP server - and it does it well. Deploy it quickly and easily, and let the rest of your stack do what the rest of your stack does well, wherever that may be.
uWSGI “aims at developing a full stack for building hosting services” - if that’s a thing you need then ok, but I like the principle of doing one thing well, and I deploy to platforms like Heroku and AWS Elastic Beanstalk where the rest of the “hosting service” is provided and managed for me.
Azure WebsitesWe use Azure's Websites to host our app and site. Continuous deployment from GitHub is the handiest feature, check in and before you know it your updated site is already online.
AWS Elastic BeanstalkElastic Beanstalk gives us a managed platform for our front end servers to make sure that traffic is never overloading our servers and that deployments are always successful.
Azure WebsitesAzure WebSites is the fully managed scalable platform for hosting web content and running background jobs.
AWS Elastic BeanstalkElastic Beanstalk manages our environments. We rely on it to manage rolling out new versions of services.
AWS Elastic BeanstalkEasy to get started. Essentially a package of several AWS products integrated for you.
AWS Elastic BeanstalkFor convenience I use Elastic Beanstalk to host all my sites.
AWS Elastic BeanstalkAll server-side deployments go to one of 5 EB environments.
Azure WebsitesSupport websites
Azure WebsitesHosting the app