This module will help you understand what DevOps is and how to plan for a DevOps transformation journey.

Source control is fundamental to DevOps. In this modern day you’ll hardly find any resistance to the use of source control; however, there is some level of ambiguity around the differences in the two different types of source control systems and which type is better suited where.

As a version control system, git is easy to get started with but difficult to master. While there is no one way to implement git in the right way, there are lots of techniques that can help you scale the implementation of git across the organization. Simple things like structuring your code into micro repos, selecting a lean branching & merging model and leveraging pull requests for code review can make your teams more productive.

In this module, we will talk about managing dependencies in software development. We are going to cover what dependencies are and how to identify them in your codebase. Then you will learn how to package these dependencies and manage the packages in package feeds. Finally, you are going to learn about versioning strategies. We will look at dependency management as a concept in software and why it is needed. We are going to look at dependency management strategies and how you can identify components in your source code and change these to dependencies.

Continuous Integration is one of the key pillars of DevOps. Once you have your code in a version control system you need an automated way of integrating the code on an ongoing basis. Azure Pipelines is a fully featured cross platform CI and CD service. It works with your preferred Git provider and can deploy to most major cloud services, which include Azure services. Azure DevOps offers a comprehensive Pipelines offering.

Gone are the days of tossing a build over the wall and hoping that it works in production. Now development and operations are joined together as one in DevOps. DevOps accelerates the velocity with which products are deployed to customers. However, the catch with DevOps is that it moves fast, and security must move faster to keep up and make an impact. When products were built under the waterfall process, the release cycle was measured in years, so security process could take almost as long as it wanted. Face it, DevOps is here to stay, and it is not getting any slower. Application security must speed up to keep pace with the speed of business. Security automation is king under DevOps.

Technical Debt refers to the trade-off between decisions that make something easy in the short term and the ones that make it maintainable in the long term. Companies constantly need to trade off between solving the immediate, pressing problems and fixing long-term issues. Both code quality and security are mostly overlooked by software development teams as not their problem to solve! Part of the solution to this problem is to create a quality-focused culture that encourages shared responsibility and ownership for both code quality and security compliance. Azure DevOps has great tooling and ecosystem to improve code quality and apply automated security checks.

Containers are the third model of compute, after bare metal and virtual machines – and containers are here to stay. Docker gives you a simple platform for running apps in containers, old and new apps on Windows and Linux, and that simplicity is a powerful enabler for all aspects of modern IT. Containers aren’t only faster and easier to use than VMs; they also make far more efficient use of computing hardware.

In this module, we will talk about how you can secure your packages and feeds and check security requirements on the packages used in developing your software solutions. Also we will cover how to make sure the packages used are compliant to the standard and requirements that exist in your organization from a licensing and security vulnerability perspective.

In this module, we will talk about Continuous Delivery in general. In this introduction, we will cover the basics. I’ll explain the concepts of Continuous Delivery, Continuous Integration and Continuous Deployment and also the relation to DevOps, and we will discuss why you would you need Continuous Delivery and Continuous Deployment. After that, we will talk about releases and deployments and the differences between those two.

Continuous Delivery is much more about enabling teams within your organization. Enable them to deliver the software on demand. Making it possible that you can press a button at any time of the day, and still have a good product means a number of things. It says that the code needs to be high quality, the build needs to be fully automated and tested, and the deployment of the software needs to be fully automated and tested as well.
Now we need to dive a little bit further into the release management tooling. We will include a lot of things coming from Azure pipelines. A part of the Azure DevOps suite. Azure DevOps is an integrated solution for implementing DevOps and Continuous Delivery in your organization. We will cover some specifics of Azure pipelines, but this does not mean they do not apply for other products available in the marketplace. Many of the other tools share the same concepts and only differ in naming.

This module is about implementing an appropriate deployment pattern.

This module is about implementing an process for routing system feedback to development teams.

This module is about infrastructure and configuration Azure Tools.

This module is about differences between IaaS, PaaS and FaaS.

The students in this module will learn how to deploy and configure a Managed Kubernetes cluster.

The students in this module will learn how to deploy and configure infrastructure using 3rd party tools and services with Azure, such as Chef, Puppet, Ansible, and Terraform.

This module is about implementing compliance and security in your infrastructure.

The students in this module will learn how to design system feedback mechanisms.

This module is about optimize feedback mechanisms.