Complimentary Services between AWS and Azure - Part I

Prathamesh Mahadik
4 min readMar 14, 2020

--

Apocalypse is upon us again, and this time its called Corona (COVID-19). Having lived through 2012 (supposed END of WORLD), H1N1, SARS, and a heart-wrenching break-up after 7 years of dating I think I will survive this stupid disease named after a cheap beer.

Nevertheless, I have to follow the WFH recommendation from offices and governments alike. I mean if Tom Hanks isn't safe, then who is right? But I am BOREDDDDD.

After having played PUBG for way longer than I should have, I decided to sharpen some of my cloud skills (specially Azure )and here is what I have to share.

You can find a bunch of posts and blogs detailing the differences between AWS and AZURE, however, there are number of similarities as well as more than a few complimentary services between AWS and AZURE. I know we have a bunch of people who know one of the cloud platforms and not the other. Therefore, this article is targeted towards such people who would like to know more about their complimentary services on the other side.

So let's just dive in with the simplest of all services — Storage :

Most of the applications need just the above storage tiers but for application needing archival storage or Block disk storage AWS and Azure offer the below variations.

Networking structures are the backbone of any applications or services both on cloud and on-premise. With both cloud rivals trying to stay as close to the network layer as possible you can easily figure out that they act and operate in a remarkably similar way providing solutions that can be a mirror to each other.

The below architecture diagram shows network components comparison between Azure and AWS.

Microsoft defines IaaS as — Infrastructure as a service (IaaS) is an instant computing infrastructure, provisioned and managed over the internet.

Both AWS and Microsoft AZURE have their IaaS offerings for a long time now. Below is a quick comparison.

A standard and well accepted definition of PaaS would be as follows -
Platform as a service (PaaS) or application platform as a service (aPaaS) or platform-based service is a category of cloud computing services that provides a platform allowing customers to develop, run, and manage applications without the complexity of building and maintaining the infrastructure typically associated with developing and launching an app.

AZURE App Service seems to be a viable alternative to AWS Beanstalk.

The next topic is by-far the most liked feature in the MICROSERVICE world :-

One of the game-changing features when launched FaaS is now the base for millions of applications and services online.
Function as a service (FaaS) is a category of cloud computing services that provides a platform allowing customers to develop, run, and manage application functionalities without the complexity of building and maintaining the infrastructure typically associated with developing and launching an app.

Building an application following this model is one way of achieving a “serverless” architecture, and is typically used when building microservices applications.

Since there are tens of services to compare and contrast, it will be easier for us to take little incremental steps. I will conclude Part I of this post here and have another go as and when the services evolve !!

Check out my previous article here:

--

--