Introduction to DevOps

Introduction to DevOps

• Diogo Sobral presented an overview of DevOps on January 7, 2025.

Meta-Agenda

• Introduction will take 10 minutes
• Emargement takes approximately 5 minutes
• The module, as a whole, is around 2 hours, 30 minutes
• There will be a live session from 08:45 to 12:00, incorporating interaction and a 15-minute break from 10:15 to 10:30.

Who is Diogo Sobral?

• Diogo Sobral is a Solutions Architect for pre-sales and delivery.
• He works at Capgemini since 2008.
• Since 2019, Diogo Sobral leads DevOps France Community
• Certified in Agile (Scrum Master, SAFe Agilist), Cloud (Azure and AWS), DevOps Foundation and Architecture TOGAF
• Diogo Sobral is a part-time teacher at Paris Dauphine since 2014 and occasionally teaches at ESIEE, ESIEA, and UTT.

DevOps Agenda

• Market, challenges, and organizations will take approximately 30 minutes
• History, definitions, and concepts will take approximately 30 minutes
• A discussion of architecture will take approximately 30 minutes
• Implementations and tooling discussion will take approximately 30 minutes
• Examples and feedback sharing will take approximately 30 minutes
• The conclusion and discussion of DevOps community topics will take approximately 10 minutes

Market Overview

• The DevOps market is a key discussion point within the market, challenges, and organizations' agenda
• Specific challenges within the DevOps space will be addressed
• Understanding the evolution of organizational models in relation to DevOps is a focus

DevOps Market Growth

• An estimated $15 billion will be invested in DevOps by 2026
• Compound annual growth rate of 19.1% predicted states a Fortune Business Insights report

DevOps Challenges and Benefits

• DevOps reduces project times across the software production chain through automation and streamlined management tools

Benefits of DevOps

• A 20% improvement in delivery time-to-market
• There has been a 17% increase in deployment frequency

Improved Quality

• Delivering stable, high-performance, products through industrialized processes and continuous improvement
• Expect around 22% increase in quality production

Costs

• Test and run costs decrease, -11% because of task automation
• Cost reduction is a result of DevOps, not its objective
• Manual tasks reduction leads to reallocating resources to value-added activities

Key Challenges

• According to Gartner, the biggest challenge for organizations expanding DevOps is people issues at 50%.

The Goal of DevOps

• To make everything continuous through eliminating waste and automating manual tasks

Software Delivery Pipeline

• The classic software creation pipeline involves requirements, implementation, build, integration, functional tests, operational tests, and production
• It involves Source code, Testing using Integration tests, functions performance and security

Production Deployments

• Web giants have perfectly mastered DevOps.
• Netflix deploys 500 times daily
• Google deploys 5000 times daily
• Amazon deploys every 10 seconds
• Facebook deploys twice a day
• Flickr deploys more than 10 times daily

Architecture Evolution in DevOps

• DevOps improves reliability on distributed systems that can be cloud native
• The architecture evolves from monolithic to microservices based

Monolithic Architecture

• All components in the monolithic architecture share a single code base

Microservices Architecture

• Each microservice operates independently for increased resilience

Deployment Methods

• Blue/Green
• Canary Deployments

Implementing CI/CD Increases DevOps Speed

• Horizontal axis represents traditional Agile IT, Continuous Integration, Continuous Delivery, Continuous Deployment
• Each stage improves development from expert at deployment

Continuous Integration, Principles

• The process must be reproducible and reliable
• Automate everything if required
• Do it more often if something is challenging
• Manage everything under Git

Continuous Delivery, Principles

• A binary code should only built once
• Always implement surface tests at each deployment
• Should an error occur, stop the process

Continuous Deployment, Best Practices

• Code should be reproducible and reliable
• Should be built once
• It needs a deployment mechanism
• Must implement surface test on each deployment

Continuous Delivery Concept

• Build Once, Deploy Anywhere

Test Automation and Quality

• Automate tests throughout the Agile mode
• Methodologies include: BDD, ATDD, TDD

DevOps CALMS

• CALMS represent five fundamental pillars: Culture, Automation, Lean, Measurement, and Sharing

CALMS - Culture

• Culture consists of Shared responsibility, Mutual support and collaboration, Start small and grow horizontally

CALMS - Automation

• Automate manual and time-consuming tasks to rapidly process user feedback

CALMS - Lean

• Rationalize operations and solve the problem.

CALMS - Measurement

• Key Performance Indicators are guide by statistics
• Use tools to measure performance

CALMS - Sharing

• It should improve sharing and communication with a process.
• Alignment with objectives
• Encouraging learning

DevOps Roles

• The following chart represents the DevOps Roles to consider, which should be tool agnostic

Reference Architecture

• Architecture in typical IT process

Development Stage of the Architecture

• Tool agnostic

Continous Integration stage of the Architecture

• Includes all relevant checks

Continuous Delivery

• Includes tools and process

Operations

• Continuous improvements
• AIOps for efficiency

Market Tools

• Terminology
• Cloud concepts (IaaS, PaaS, SaaS) and
• Containerisation
• Tools and platforms on the market

Software factory

• A set of tools

Containerization

• Container vs Virtual Machine

Cloud Deployment

• On-Premises
• IaaS (Infrastructure as a Service)
• PaaS (Platform as a Service)
• SaaS (Software as a Service)

Cloud Allegory

• The allegory of Cloud Piza Models: Dining, Fire and Toppings

Cloud Native Structure

• The structure represents components and its relative position

Infrastructure Scaling

• Scaling is done using both horizontally and vertically

Most Used Tools

• Review the tool market before committing to the architecture

Implementation Examples

• Demonstrates some of the example implementations.

Role Implementation

• What to avoid, or common mistakes and goals.

DevOps

• Movement
• Philosophy
• Breaking
• Collaboration

Conclusion

• The presentation lists traps to avoid, by getting a sponsor, thinking about security, understanding your customers and more.

France DevOps Community is the final item in this DevOps introduction presentation.

• Birth of community was in 2019, and the first planned community launch in 2020