DevOps Principles &

Practices
DevOps Series
pengertian devops

ⓘ Start presenting to display the poll results on this slide.

teknologi/tools devops yang ada ketahui

ⓘ Start presenting to display the poll results on this slide.

BUSINESS CUSTOMER
BUSINESS CUSTOMER

#1
treat Dev & Ops as
the same system
PRINCIPLES
• Visualize the flow of work to understand the system
• Never pass a known defect downstream
• Never allow local process optimization to create a global
degradation
• Review and optimize to increase flow
#1
treat Dev & Ops as
the same system
PRACTICES
• Create rapid feedback loops through Automated Testing and
Continuous Integration of code
• Minimize your Work-In-Progress (WIP) by using Continuous
Deployment to push small changes to production as frequently as
possible – this makes the process highly repeatable and reliable
#1
treat Dev & Ops as
the same system
PRACTICES
• Invest heavily in paying down Technical Debt and improving Code
Maintainability to reduce the drag it places on all development and
operations practices
• Create environments on demand by using highly automated
Infrastructure-as-Code (IaC) deployment everywhere
#1
treat Dev & Ops as
the same system
#2
focus on the flow
of work
PRINCIPLES
• Shorten and amplify all feedback loops
• Respond to all customers - internal and external

#2
focus on the
flow of work
PRACTICES
• Elevate the improvement of processes over daily work through the
use of structured Problem Solving, and "stop the line" or “andon”
processes

#2
focus on the
flow of work
PRACTICES
• “Shift-left” testing using practices like Test First development (TDD
& BDD ) to build comprehensive, fast Test Automation suites
• Creating shared goals (and pain) for Dev and Ops teams by making
all parts of the process highly visible – including operational
performance and customer feedback. #2
focus on the
flow of work
#3
focus on building the culture
of continual experimentation
and learning
PRINCIPLES
• Promote experimentation
• Learn from success and from failure
• Respond quickly to change
• Exploit new opportunities
#3
focus on building the culture
of continual experimentation
and learning
PRACTICES
• Encourage innovation and risk taking via autonomous Product
Teams by giving them Flexible Working arrangements and
encouraging your engineers to become masters of their art through
targeted Learning and Knowledge Sharing
#3
focus on building the culture
of continual experimentation
and learning
PRACTICES
• Exploit opportunities such as incidents to constantly test and
improve your Disaster Recovery which will drive reliability and
reduce friction in operations
• Use hypotheses, backed by data, to experiment,
fail-fast and uncover new high-value opportunities #3
focus on building the culture
of continual experimentation
and learning
 Infrastructure as Code
Source Code Provisioning
Version Control Configuration Management

Code Deploy

Operate
Development Virtualisation
Build

Automation Containerisation

Test Monitor

Continuous Integration/
Continuous Delivery or Visualisations
Deployment (CI/CD) Logging
Quality Control
© 2021 INIXINDO
Software Delivery & Operational (SDO) Metrics
Environment Factors to Support SDO

Cloud Technology
Psychological
Safety

Loosely Coupled
Architectures

Tools
DevOps CI/CD
DevOps Series
CI/CD
Code
commit Unit and
(multiple integration Functional Configuration
developers) testing testing automation Deployment

Build Create User Load testing

application acceptance
or service testing
image

Continuous Integration (CI) Continuous Delivery (CD)

CI (Continuous Integration)
repository
CI (Continuous Integration)
repository
CI Server BUILD

TEST

RESULT
CI (Continuous Integration)

Code Management
$ git push

$ git pull

Local Remote GIT

repository repository
CD (Continuous Delivery)

v. 1.0

v. 1.1
CD (Continuous Delivery)
database
Continuous back-end
hands-off cluster
push deployment

web
socket
cluster

© 2021 INIXINDO
CD (Continuous Delivery)

© 2021 INIXINDO
CD (Continuous Delivery)

© 2021 INIXINDO