Explore the ways to analyze a cloud system. Learn how cloud service and deployment models can affect cloud deployment and applications.
- [Instructor] Analyzing cloud applications. When it comes to deploying resources in the cloud, it's important to understand that companies are choosing to go to the cloud for several reasons. The first is the cloud is changing the way enterprises procure IT. The days of companies procuring equipment and placing that equipment in their data center is slowly coming to an end in a lot of organizations.
Companies are now choosing to essentially go to more of an OpEx model. The second reason is companies are essentially looking at the cloud as a business decision in most cases. Companies are looking to reduce their infrastructure costs, to increase their time to market, and to make their employees' days more efficient. And the third reason is that cloud computing typically requires a paradigm shift for IT as well. IT now has the opportunity to become more of a strategic enabler.
When it comes to analyzing applications, understand that there's certain areas that you may want to look at. User requirements. When it comes to user requirements, several factors may come into play here. For example, is the user remote or is the user local to the organization? Is it content delivery? Is it not content delivery? Costing models. When it comes to costing models, companies are looking at the costs that are involved for developing and deploying applications, but also for maintaining those applications.
Is the solution a cloud fit? For example, if a company is going to choose to deploy a CRM app, and Salesforce fits 95% of the requirements, chances are the company isn't going to go and develop a new application where Salesforce would fit the bill for 95% of their requirements. Compliance is another area that typically requires a lot of focus as well. Security and performance are also other areas that companies need to really look at to determine the feasibility of deploying that application to the cloud.
When it come to cloud application analysis, there's essentially two accepted methods. The first is static. This is essentially strings and APIs, but typically this won't be deployed in a run-time environment. In other words, the application is not effectively running in production. And then dynamic. Dynamic is essentially where the application is essentially running in production.
For example, you could use Stackdriver to help analyze and debug an application. That's a very common tool that you see in a lot of organizations. When it comes to analyzing system methods, you want to look at numerous areas. Some of these would be the application requirements itself, the workload types, so for example, some workloads are very steady, whereas some workloads are very burst-y. Performance.
For example, is this a VDI environment, or is this a production application where you need sub-millisecond requirements for latency, for example? You need to determine if this application is going to be a cloud fit, or is it not. Security. Here's certainly an area that companies really need to focus on. Functionality. Functionality is another area that typically companies need to really look at, and determine how much functionality is required, but also too, does a functionality provide additional value? When it comes to analyzing systems, there's essentially several different service models that we want to look at.
Infrastructure as a service. For example, are you deploying a VDI environment, or a big data service? Platform as a service. Are you developing applications and testing those applications in the cloud? Software as a service. Essentially are you using a cloud fit solution like Salesforce or Office 365? Business process as a service could be a Salesforce solution, but could also be more focused, mainly around accounting or a specialized area.
When it comes to analyzing systems, you also should look at how that cloud is deployed. Is it private? Is it public? Community? Or hybrid? Now hybrid cloud is essentially where you're taking two or more of the deployment models and using Federation, and Automation, and Orchestration, to essentially integrate directory services and other capabilities. There are two types of ways to analyze applications: static and dynamic.
Here is an exam tip. Know the difference between the service models: infrastructure as a service, platform as a service, and software as a service.
Whether you're a network administrator, cloud developer, or cloud specialist, holding the CompTIA Cloud+ certification can enhance your career by demonstrating to potential employers that you have a solid understanding of how to implement and maintain cloud technologies. This course can prepare you for the qualifying exam by covering the topics outlined in domain 1.0 of the CompTIA Cloud+ (CV0-002) certification exam: Configuration and Deployment. Instructor Joseph Holbrook reviews concepts that can help both experienced IT professionals prepping for exam CV0-002, and current certification holders who need to renew their certification. He explains how to analyze system requirements for deployment, establish baselines for analysis, and implement deployment plans. In addition, he explains how to size your cloud requirements around the correct scaling model, analyze appropriate storage types, troubleshoot configuration and deployment, and more.
- Analyzing system and application requirements
- Establishing baselines for analysis
- Implementing deployment plans
- Basic testing analysis
- Establishing a standard operating procedure
- Determining success factors around testing
- Analyzing network configurations