Amazon EC2 vs. Microsoft Azure vs. ElasticHosts Cloud Servers

About a year and a half ago (written June 2013) we moved from dedicated servers over to AWS. Thanks to AWS, we no longer have to think on a server level. Instead, we think of everything as a cluster of instances, and an instance is essentially a virtual server where we don’t have to worry about the hardware. It’s a relief to not have to worry about the hardware behind the instances.

The clusters we have are: WWW, API, Upload, HAProxy, HBase, MySQL, Memcached, Redis, and ElasticSearch, for an average total of 80 instances. Each cluster handles the job that its name describes, all working together for the common goal of giving you your daily (hourly?) dose of image entertainment.

Below is a diagram of how they all work together:

Our app servers are served from EC2

App servers, celery VMs, and a number of internal supportting systems run on EC2.

Almost all our servers run from Ubuntu on AWS EC2, as it is robust and easy to work with.

We're in the process of moving to a SOA (service-oriented architecture), and each of our services run on a cluster of EC2 boxes behind an ELB. Our services are built primarily with Go and Ruby, depending on the requirements.

All backend instances

We liked a lot of things about Heroku. We loved the build packs, and we still in fact use Heroku build packs, but we were frustrated by lack of control about a lot of things. It’s nice to own the complete stack, or rather as far down as AWS goes. It gave us a lot of flexibility and functionality that we didn’t have before. We use a lot of Amazon technology.

Pretty much all the things.

Opstax uses EC2 in replacement for traditional physical infrastructure.

We have over fleet of over 25 servers running at any given time that scales elastically with load.

For hosting and scaling our infrastructure based on demand.

모든 서버는 EC2 를 이용하고 있습니다. 가격이 저렴하다고는 할 수 없습니다만 신뢰성 있고, 관리가 아주 편리합니다. 원하는 만큼 순식간에 서버를 증설했다가 필요없을 때 바로 반납해버릴 수 있기 때문에 스타트업에서 이만한 IaaS 를 찾을 수 없다고 생각합니다. 저희가 사용하는 지역은 도쿄입니다.

It provides our cluster in a VPC

We use Amazon EC2’ to obtain and configure capacity.

host nifi and node.js

Various Activities.

To host VoicePing users management / login server and messaging router stack

Site hosting.

When you need flexibility with compute power, memory, EBS, snapshots, security groups, etc.

For running the application

The site is hosted on an EC2 instance.

Stack infrastructure

Cloud Infrastructure

Servers!!

We host our website here

Just for tuneling to RDS as a "bastion".

Where this app is deployed.

We use EC2 in some client projects.

We use this both indirectly through Elastic Beanstalk and directly for running some servers continuously. AWS is a solid provider of cloud services.

ec2에 우분투를 사용합니다. 로드 밸런싱 등의 경험은 아직 없습니다. 지금까지는 배포하기까지만 경험했습니다.

Auto-scaling region-distributed application hosting.

Our server nodes we hosted on EC2

Runs our ELB and container services

We use several EC2 instances each dedicated for a separate purpose - API servers, TCP servers for device, DB instances.

Cheap server hosting for the status page

Hosting my personal website.

Bastion host

basic

Server host

Cloud hosting.

currently using it play around with machine learning. the p2 instances have a tesla card in them!! not too bad for .90c an hour.

We use ElasticBeanstalk to manage the applications/deployment/scaling functionality over top of EC2.

There are a few smaller ec2 instances that are customized for the multiplayer system.

Audit the EC2 configurations for best practices and standards.

Cloud hosting

Amazon offers free use of an ec2 micro instance for 1 year

Integrating Amazon's many AWS services, such as RDS, is a breeze if you're using EC2.

kako.pk's web server host

Server apps.

VM hosts for Vaultize public cloud.

The same reason everyone else uses it, data crunching or websites.

We use EC2 to run our Kubernetes cluster.

Because servers. Lots of them. Lots of configurations. Great for mission-specific functions. Video encoding, data aggregation, dedicated processing, mission-critical data stores. Anything you can't hang off your Heroku environment.

The engine running it all

We host most of our infrastructure on AWS currently.

EC2 runs our application servers - the servers that do all the heavy lifting for CloudRepo.

We use EC2 to host our web services.

provisioning & deployment

Virtual Machines

We use EC2 to provide and run our NodeJS infrastructure on prod env.

The most efficient elastic cloud computing service.

Secondary jobs.

Reliable, cheap and pay on demand. I used it for data training with machine learning techniques.

Deployment

GPU servers

Storage

The Seen on Set website is hosted with Azure. We use SQL Azure for structured data persistence and Azure Web Apps is used to host the main web application.

Cloud platform to host the solution

Hosting the server and the backend

Azure is used for deploying the bot to the cloud as a fallback to hardware device deployment.

We currently host PRS and EARS on Azure as they are .Net apps, but we are currently porting these services to Scala and will be hosting them on Heroku with the other P2 SRX services.

Serviço utilizado para deploy de toda a infraestrutura do projeto. Colocamos todas as peças do serviço no azure, garantindo uma forma rápida e garantia de escalibilidade.

We are using virtual machines and now Kubernetes via their ACS (Azure Container Service) to make it scalable and highly available.

Experience with the IoT Hub and the Azure Event bus. Also using Azure as storage provider for personal backup system.

8GB, SSD VMs run the crawlers

Cloud hosting

Blackbaud makes use of Azure and my current job is with Blackbaud. Therefore, due to the free credit and the ability to reuse tools, I rely on Azure quite a bit.

My favourite cloud with all the great tools - web apps, mobile apps, storages, easy tables, blobs, app insights, cosmos DB... I think it is really usable and ergonomic. Plus point for mobile app.