Folks at AWS publish a really great resource for anyone, who is designing cloud architecture. Even if you are using already or thinking about Azure or GCP, it is a really good read and it is not your typical sleep-provoking dry white-paper.
AWS did an awesome job packing a lot of practical recommendations, best practices, tips, and suggestions into this document.
AWS Well-architected framework focuses on 5 pillars:
- Operational Excellence
- Performance Efficiency
- Cost Optimization
What really impressed me is how they teach customers to avoid "unneeded" costs. Working for many years with traditional "enterprise" vendors, I was very surprised to see real and practical tips to actually save money for their customers.
I mean, do not they want to make more money on stupid decisions and sky-rocketed IT budgets and costs? How many of you were in these meetings with vendors and one of the first questions they would ask is "what is your budget" so they can have most of it?
Needless to say, I did not believe what I had read and conducted my own investigation. I read numerous conversations between AWS-employed architects and engineers. I went to glassdoor, and I read reviews from AWS solutions architects and engineers. It became evident to me that these guys really stand behind these ideas and they mean it.
And you know why? Because of that magical LP thing! You will see this abbreviation everywhere. LP stands for Amazon Leadership Principles! It is a real thing for them, not just loud words posted on a wall in executive offices. They are easy to understand, some of them a bit contradictory to others (I guess intentionally), but many of us, technical folks, can relay to these principles.
Another extremely helpful document is Analytics Lens. It expands on the ideas of the AWS Well architected framework to apply 5 pillars to Big Data and Analytics architecture.
While all the pillars are important and needed, the great focus is given to the Operational Excellence one. Not surprisingly, we are all know how effective Amazon is at running their infrastructure and warehouses.
Lastly, Big Data Analytics Options on AWS document explains all the AWS-native services, specific to Big Data Analytics. In the Amazon LP spirit, the author generously suggested ideal usage patterns and anti-patterns, focusing greatly on cost efficiency again.
Well done, AWS team!