 In this module, I will talk about the 10 reasons or the 10s for the Amazon web services and this module of course is not possible to cover those 10 reasons for the design with reference to a cloud and why the users use Amazon web services. This is just an intro and this module I will just very very briefly talk about some of those aspects among the 10 and towards the end of this course we will be spending a lot of time on all of those 10s. So without further ado, when people ask why certain the programmers they are using Amazon web services, they are unable to describe why they are using it or maybe sometimes people are interested or they are inclined about using the Amazon web services but they cannot spell out the reasons why they want to use the Amazon web services and of course then there are people or the programmers or developers who are in fact using the Amazon web services but when the management ask them that why they are using Amazon web services, they are kind of tongue tied. So that is one aspect of Amazon web services which of course is the strength of Amazon web services. So what I will do is briefly talk about in the details of these modules that what are the 10 main fundamental reasons or the strengths of Amazon web services. Now the second aspect is the design aspects or the cloud aspects of the Amazon web services. Now for example, people will say or tell you that use the right tool for the right job. So the right tool for the right job in the context of the web applications, in terms of the scale of the web applications, they require the processing power. So Amazon web services is the tool, is the tool, so the tool for example Pinterest. So a lot of images, hundreds of thousands of millions of images and visitors, so they are using Amazon web services. Then of course is the one should have the skill to select the right tool for the right job. So what is that skill? That skill in the context of Amazon web services is that you should know that which service or the characteristics of the service is suitable for your application design. And then of course, it's a combination of these things, which results into a design which I will tell you the 10 reasons why and what are the considerations for the cloud aspects of the Amazon web services. So these are the 10 reasons, of course, it's not possible to go through all of those 10 reasons. I will just go through the IT agility of the Amazon web services, the cost considerations and it is good for your career. So let me first talk about the IT agility, IT agility of the Amazon web services. Now in the context of the IT department, people will say kind of jokingly on a lighter note that the IT department is the no department. Now if you ask them to provide services and resources, they will they will have many issues, they will have many procedures, they will have many processes. And those procedures and processes have developed over a period of time. And they are kind of failsafe processes and procedures. But as a consequence of those processes and procedures, is that if I need processing power, okay, I have to go through a lot of hurdles, a lot of roadblocks and a lot of barriers, and it can take months, it can take weeks before I get the processing power which I need. But with the Amazon web services, that processing power is there. I don't have to go through all those hurdles. I don't have to go through all those impediments. I don't have to go through all those barriers. That processing power is is there. And as this as the point I am going to discuss right now which is underlined it is cost effective. Amazon web services are cost effective in terms of processing power. There are hardly any penalties. And I can use this services and I am billed for what I have done. And when I'm through, I can stop using those services. And when I want to use the services again, I can again refer back or use those services again. So they are cost effective. And they are they have the agility also. And then with reference to the carrier. What is most important is you, your carrier, right? So you have to develop an understanding which I will also talk about and discuss and explain also that what are the different types of Amazon web services and develop an understanding in a thought process of aligning the application needs with the characteristics and applications of the Amazon web services. So that you have a productive career, we'll talk more about it. Everything fails at the time. So design principle for the cloud. Now, there's something is called as the Murphy's law. Murphy's law says that if something is going to fail, it is going to fail, right? And it is going to fail in addition at the worst possible time with very painful consequences. So the one aspect of Amazon web services for the cloud is that things fail. Things fail because in the traditional IT setup, there's a lot of effort which has which which has gone into and is going that the applications stay. They don't fail that the infrastructure stays. It doesn't fail. But the thing is that they do fail and when they fail, then the IT department people they put in extra effort to to add redundancy in the system. But still the system will fail. So it is just kind of running about trying to make a perfect system, which is not there. But with the Amazon cloud, we we know we we understand and we work with the understanding and the concept that things fail all the time. And then is the monitoring the problems. Now, if I have a redundant system with redundancy, a very nice system. But if the system component fails, application fail, part of the infrastructure fails, then that nice redundancy is gone. It is gone. So I have a non redundant system. So how to prevent it by monitoring when I monitor it. And there are prediction models also, which can predict when something is going to fail, which is part of business intelligence. I can make preparations. I can have a more proactive approach instead of a reactive approach to address those requirements. And then of course is the tier based design approach. Now, usually if I divide partition the security groups, then I have a secure tier, right? But something which is kind of overlooked is that if I have redundant resources and I have a flexible tier, then what I can do is that as per the requirement, I can have a strong tier. I can have strength with it and I can remove things and I can add things. So that increases the efficiency of my design and goes along with the Amazon web services. That's all I have to talk about in this module.