Define your own requirements for DevOps and cloud computing.
- [Narrator] So how do you understand you own core requirements for development and operations, or DevOps as it relates to Cloud computing? Well, I have three concepts that we introduced in a previous video, but let's dive deeper here. We have Agility, Cost Efficiency, and Quality. The requirement of Agility should be the ability to increase velocity of innovation. So this is about freeing people up to make decisions that are going to improve the software systems that they're building. They support faster time to market from the idea creation to the launch. In other words, we're not waiting to deploy things.
Things can happen, in essence, at the speed of need. Or basically, from the requirements that come down from the business, until the time it takes for us to solve the problem. Provides us with the ability to leverage Cloud platforms. Provide us with the capabilities of expanding up, or expanding back as the needs of the applications dictate. Faster and easier migration of core infrastructure and applications. And that between data centers and Cloud computing environments. So ultimately, this is about integrating various source and target systems are able to communicate one to another in better, more effective and efficient, ways.
And we're able to exchange information, and share information, and share services. So we're able to make software more agile to adapting to the needs of the business. Faster and easier integration of new acquisitions. The ability to buy companies and expand market shares. And one of the things I consistently hear from CEOs is that the IT is the fundamental limitation of their business. They can build a product line in a couple of months. They can move their whole business to a new building in a couple of months. But it takes about two years to integrate new business acquisitions and get them up and running.
Cost Efficiency means that we're increasing overall IT efficiency. Reduction of unit cost for the core infrastructure. Ultimately, we're able to do more with less, and operate at a much more effective and efficient way. So in other words, DevOps removes cost of development. It should, really, as an instate objective. But Cloud is also able to provide us with an infrastructure that's going to much more cost effective. We're only paying for what we going to use within the Cloud, we're not paying for hardware and software. Able to increase development productivity, including key improvement layers, and standardization of core infrastructure.
We're able to leverage standardized ways and templates for developing software, and adhering to needs, and rules, and all these other things that we have to follow as we move a business into an automated state. Able to provide high automation of everything. And then a simplified procedures for in self service for organizations, end users, developers. So they can get what they need to be productive as they need it. And we've all had latency around sitting around waiting for new computing systems to show up.
And that needs to be removed from the process. And this is about becoming more cost effective and cost efficient by doing that faster through the procedures and self service. The ability to increase asset utilization through resource sharing. We're able to leverage Cloud-based systems, not only as a mechanism to eliminate us from buying hardware and software, but the ability to share resources in a much more effective and cost-efficient way. So, as we're leveraging a Cloud with thousands of other users, and sometimes thousands of other companies, the utilization of those resources is much more cost efficient than it is than maintaining you own hardware and software.
And then a high degree of application component reuse as well. Finally Quality, which is very important, provides a higher core infrastructure and application resiliency and availability. So that's the core measure. So it's about the ability to, in essence, keep applications running to meet the needs of the business and meet the needs of the end user. Make them available at all time, and make them completely resilience. In other words, even if there's a natural disaster that occurs, they should never stop running. So the ability to leverage Cloud-based systems, the ability to leverage DevOps, should have the objective of building applications that never fail, never crash, never stop the business from running because they're failing to produce the value that they need to produce.
Improved maintainability of infrastructure and applications refers to the fact that we're going to make them not only better and higher quality, but they're easier to maintain. So the operations side of DevOps is able to back up systems easier, able to move information systems into production easier. And the ability for the applications to, in essence, work and play well together with the existing operations infrastructure, is a factor of quality. High consistency among applications. Applications are never going to be burdensome because they're dealing with different language supports, different structures, different ways of doing something.
This is about, in essence, your capability of driving the applications into a highly consistent state, which means there's synergy between the applications and how things are built. And this allows other developers to work on other applications without a higher learning curve. But it also allows us to become more quality-obsessed in how we build and deploy those applications. Finally, increased levels of security as a bar is raised to publicly hosted applications. So as we're moving systems into the cloud, security's going to be a primary concern.
Cause we're running them on platforms that we don't control our own. And so, security needs to be systemic to all of this.
- DevOps on the cloud
- Continuous delivery, testing, integration, and deployment
- Creating your own DevOps processes
- Defining logical and physical processes
- Selecting cloud services: AWS, Google, Microsoft, and others
- DevOps use cases