In my last post, I made a cheat sheet to help cloud architects translate services between Microsoft Azure and AWS. It was well-received by the community, and I thought of ways how to make these translations more useful for the community.
If you're like me, I've been working between Azure and AWS, and it's starting to feel like working between two programming languages, like JavaScript and Python. I find it a good and useful exercise to keep abreast with the analogous services between the two major cloud platforms. (Multi-cloud folks would have a different opinion on this, but I digress.)
Azure Reference Architecture
A possible way to make this translation more tangible is to take a look at existing architectures and see what it looks like with another cloud service. I found this simple and elegant serverless web application architecture from Azure:
Translated AWS Architecture
I translated the Azure-based application into AWS and here is what it looks like:
Let's do a quick breakdown of the AWS services:
- S3 - This is where the static files will be stored, like HTML, CSS, and JavaScript files.
- CloudFront - We will use this as our Content Delivery Network to enable caching content and accelerate delivery of content, as well as providing an HTTPS endpoint.
- Lambda - The key engine that makes this work.
- API Gateway - As the name implies, it will provide as the access point for the application.
- RDS - The application's data store.
- Single Sign-On - This is the equivalent to Azure's Active Directory for user authentication.
- CloudWatch - Although not technically part of the application, this helps us monitor the performance and infrastructure data collection.
- CodeDeploy - Modern web applications need a seamless and easy workflow. CodeDeploy is the tool for the CI/CD for building, testing, packaging, and deploying.
In closing, I hope this helps you see Azure to AWS translation more than just a conversion, but also provide some insight on how these services integrate.
Top comments (0)