Now, we gonna shift to the AWS and we will discuss some of the benefits of AWS. It was first on the market and it has the massive scale which allows them to save a lot of costs and offer those low costs to the end users such as you and me.
They're quite the innovators in terms of delivering new APIs, features, services. There are a lot of skills and a lot of best practices and tooling around AWS and it's almost a standard if you go and try to hire someone, or if you try to hire a firm that does consultancy or you're looking for a job yourself, it's de-facto a standard in the cloud, the AWS services and AWS tools.
Some of the best practices for cloud computing. You would apply horizontal and vertical scaling for that, you would need to have your nodes, your servers to be stateless. The less state you save in an individual instance, the easier it would be to scale it.
And you would use automation for that and also you would use automation to build redundancy and to replicate in multiple regions across continents and countries. This applies not just to an EC2, you can leverage services. Instead of deploying your own database using EC2, for example, you can use an RDS service. Build your architecture as loose coupled as possible. Have individual parts of your architecture stateless, so you can scale individual parts without having to scale the entire thing.
And then, utilize automation, you can use User Data, CloudFormation and other services and tool that AWS provides. Optimize the cost. Implement the caching.
There's a good whitepaper, it's called Well-Architectured Framework. You can download it from the repository or also it's available on amazon.com as a Kindle. It has few pillars that you need to be aware of and the basic idea is that your well-architectured framework will allow you to build and deploy faster, to lower risks, make informed decisions and also you need to know what services where to use. So, speaking of those five pillars, first and foremost is security, that's number one. It's the most important pillar of a well-architectured framework.
Number two, that's reliability.
Number three, performance efficiency.
Number four, cost optimization and number five, operational excellence, which includes maintenance and speed to market. And each particular infrastructure at a given time could have multiple factors considered when you use this well-architectured framework to analyze that infrastructure. And it's always changing, so you need to constantly reevaluate using those pillars and in that whitepaper, they would also explain you, what are the best services to use for which pillar and how, what is the best approach to do that.
And of course, there is no binary, right or wrong, typically you will have some combination, so it's not like all your infrastructure is well-architectured and that one is not, sometimes you will end up somewhere in between. And with the certain recommendations, if you follow that framework.