Module 1 - Introduction to DevOps

Essential DevOps practices

- Agile planning - Continuous integration - Continuous delivery - Monitoring of applications. DevOps is a constant journey.

DevOps Transformation

- Availability of staff. - How the organization currently operates—implementing existing processes and procedures to support current business outcomes. - For DevOps transformations, the separate team should be composed of staff members. Focused on and measured on the transformation outcomes and not involved in the day-to-day operational work. - The team might also include some external experts that can fill the knowledge gaps—also, helping to advise on processes that are new to the existing staff members.

Several advantages of shorter timelines

- It is easier to change plans or priorities when necessary. - The reduced delay between doing work and getting feedback helps ensure that the learnings and feedback are incorporated quickly. - It is easier to keep organizational support when positive outcomes are clear.

Agile planning and lean project management techniques

- Plan and isolate work into sprints. - Manage team capacity and help teams quickly adapt to changing business needs. - A DevOps Definition of Done is working software collecting telemetry against the intended business goals.

Outcomes should include specific, measurable targets

- Reduce the time spent on fixing bugs by 60%. - Reduce the time spent on unplanned work by 70%. - Reduce the out-of-hours work required by staff to no more than 10% of total working time. - Remove all direct patching of production systems. - Provide more excellent customer value, so outcomes should have a customer value focus.

Adopt DevOps practices

- You shorten your cycle time by working in smaller batches. - Using more automation. - Hardening your release pipeline. - Improving your telemetry. - Deploying more frequently.

Monitoring and Logging of running applications

Including production environments for application health and customer usage. It helps organizations create a hypothesis and quickly validate or disprove strategies. Rich data is captured and stored in various logging formats.

Continuous Delivery (CD)

Of software solutions to production and testing environments helps organizations quickly fix bugs and respond to ever-changing business requirements.

Public and Hybrid Clouds

The cloud has removed traditional bottlenecks and helped commoditize Infrastructure. You can use Infrastructure as a Service (IaaS) to lift and shift your existing apps or Platform as a Service (PaaS) to gain unprecedented productivity. The cloud gives you a data center without limits.

Optimize validated learning

The more frequently you deploy, the more you can experiment. The more opportunity you have to pivot or persevere and gain validated learning each cycle. Think of it as the sum of progress that you achieve and the failures that you avoid.

Containers

The next evolution in virtualization. They're much more lightweight than virtual machines, allow much faster hydration, and easily configure files.

Microservices architecture

Use to isolate business use cases into small reusable services that communicate via interface contracts. This architecture enables scalability and efficiency.

Version Control

Usually with a Git-based Repository, enables teams located anywhere in the world to communicate effectively during daily development activities. Also, integrate with software development tools for monitoring activities such as deployments.

Validated learning

Your cycle time determines how quickly you can gather feedback to determine what happens in the next loop. The feedback that you collect with each cycle should be factual, actionable data.

What is DevOps?

DevOps combines development (Dev) and operations (Ops) to unite people, process, and technology in application planning, development, delivery, and operations. DevOps enables coordination and collaboration between formerly siloed roles like development, IT operations, quality engineering, and security.

Continuous Integration (CI)

Drives the ongoing merging and testing of code, leading to an early finding of defects. Other benefits include less time wasted fighting merge issues and rapid feedback for development teams.

Infrastructure as Code (IaC)

Enables the automation and validation of the creation and teardown of environments to help deliver secure and stable application hosting platforms.

Pivot or Persevere Approach

Roughly one-third of the deployments will have negative business results. Approximately one-third will have positive results, and one-third will make no difference. Fail fast on effects that do not advance the business and double down on outcomes that support the business.

OODA (Observe, Orient, Decide, Act) loop

Start with observing business, market, needs, current user behavior, and available telemetry data. Then you orient with the enumeration of options for what you can deliver, perhaps with experiments. Next, you decide what to pursue, and you act by delivering working software to real users. You can see all occurring in some cycle time.