2. Agenda
• Introduction
• Digital Transformation
• Application Architecture – N-Tier, Microservices, Containers.
• Software Delivery Process – Waterfall, Agile, Agile + DevOps.
• Infrastructure – On-Premises, SaaS, Cloud, & Hybrid.
• Challenges
• What is DevOps?
• Definition
• Keep CALMS and embrace DevOps Culture.
• Process
• Reality Vs Myth
• How DevOps Culture Changing Software Delivery?
• DevOps Business Benefits
• How to start?
• DevOps Culture Challenges & How to Solve it!
• DevOps Trend 2020 - 2021
• Recap
• Q & A
3. Cloud Security, DevOps Emerging as
Enterprise Priorities
• Survey held by 2nd Watch, a provider of IT Services made this survey during Covid-19 pandemic. This survey
participated by more than 100 IT Directors.
• Three-quarters of respondents (75%) said they are prioritizing cloud security, followed by cloud-native culture change
as known DevOps, (60%) and conferencing/collaboration (51%).
75%
Cloud Security
60%
DevOps
51%
Collaboration
• This reflects the growing need to support remote workers and need more talent can can do multitasking works.
• We need more collaboration and culture change during pandemic or New Normal.
• Report here.
4. Digital Transformation
How do you enable Digital Transformation? It require evolution in;
New ways of developing,
delivering, and
integrating applications
Applications
Modernize existing and
build new cloud-based
infrastructure or do
Hybrid infrastructure.
Infrastructure
More agile process
across both IT and
the business
Process
5. Application
Monolith N-Tier Microservices
● Shift from monolithic applications to microservices
● Independently deployable and updatable, limited dependencies.
● Optimized for agility & accelerated time to market.
● Most of modern organization has their own API to integrate with any 3rd-party or external
services.
6. Infrastructure
Datacenter
● Shift from virtualization to scale-out cloud infrastructure
● Rapid growth in public cloud usage for enterprises
● Hybrid cloud deployments span private & multiple public clouds
Hosted Hybrid
9. Waterfall
• Often time Business Requirement changes and the Dev team need
to re-do all again.
• Give a lot of uncertainty and confusion to the Dev/Both teams.
• The small changes can lead to a lot of time to delivery/complete a
feature/project.
• End of the day, it can contribute to over-budget, project behind
schedule and worst the project failed to deliver to the client/deploy
to Production.
11. Agile
• IT Ops team facing problem after Agile
• They confuse and not align with the Dev anymore.
• Agility and Speed not match they normal nature anymore.
• No collaboration create more confusion between the teams.
12. Development
(Software Engineering) DevOps
Operations
(Quality Assurance)
What is DevOps?
DevOps is a set of practices that combines software
development (Dev) and IT operations (Ops). It aims to shorten
the systems development life cycle and provide continuous
delivery with high software quality - Wikipedia
DevOps breaking the silo between Dev and Ops teams and
start to working together from development to production
phase while maintaining high quality.
New way of working!
Simple Word:
13. Operate
(Monitor)
Plan
(Requirement)
Code
(Source Code
Management)
Build
(CI Tool)
Release
(Artefact
Management)
Deploy
(CD Orchestration)
#1 Plan
Business requirement
and plan the Sprint base
on the requirements.
#2 Code
Code using source code
management (SCM) &
develop code and test,
what business wants.
#3 Build
Build the code in a
deployable artifact and
test in Pre-Production
environment
#4 Release
Release the artifact as
production ready after
changes Approval
#5 Deploy
Deploy the artefact into
Production env.
#6 Monitor
Monitor the application
for its performance,
security and compliance
DevOps Process
Continuous Deployment /
Delivery(CD)
Continuous Integration (CI)
15. General Workflow of DevOps CI/CD
Pipeline
#6 Operate
#1 Plan
#2 Code
#3 Build #4 Release #5 Deploy
16.
17. Culture Automation Lean Measurement Sharing
There is a culture of shared
responsibility.
Data is collected on everything and
there are mechanisms in place that
provide visibility into all systems.
There are user-friendly
communication channels that encourage
ongoing communication between
development and operations.
Team members seek out ways
to automate as many tasks as
possible and are comfortable with
the idea of continuous delivery.
Team members are able to
visualize work in progress (WIP),
limit batch sizes and
manage queue lengths.
C A L
M S
The C.A.L.M.S DevOps Framework
18. Reality VS Myth About DevOps
•New way of working , hence it can
apply to all industry as well. (mindset /
culture )
•Automation is part of DevOps
culture/process that can speed-up and
delivery more products.
•Having DevOps in your title doesn't
make your problem solved. It’s a
journey.
•You can use any kind of solution as
long as you practice DevOps
methodologies.
•DevOps doesn't have 1 solution for all
organization.
• DevOps only for Dev and Ops team.
•Adopting tools makes you DevOps.
• Having DevOps in your title means
you're already doing DevOps.
•DevOps using Cloud solution.
•Best Practice of DevOps
20. How DevOps Culture Changing Software
Delivery?
Start Small Launch Early Fail Fast
Collaborate
Continuous
Improve
21. The Business Value of DevOps
Rapid Innovation
Faster Time-To-
Market
Customer-Centricity
22. How To Start DevOps Transformation?
Improve DevOps
Knowledge,
communication
and cross-skilling.
Evaluate new
process to
support DevOps
culture.
Re-evaluate and
rebuild
software/service
delivery cycle.
Evaluate new tech
to support
DevOps.
Just do it small
and keep simple.
23.
24. Challenge of DevOps
Dysfunctional
Culture
Resistance to
Change
Lack of Clarity
No
Collaboration
Environment
are not
Standard
Toolset Wars
No Proper
Release
Management
Manual Testing
is Onerous &
Time
consuming
25. How to Handle DevOps Challenges
Implement
DevOps Culture
Addressing
Resistance to
Change
Bringing Clarity
to DevOps
Vision
Create Cross-
Team
Collaboration
Provide
Standard
Environments
Standardizing
Tools
Accelerating
Release
Management
Automating
Testing
26. The DevOps Trend 2020 - 2021
AIOps DevSecOps Observability Site Reliability Engineering
(SRE)
27. Recap
● The benefit of the DevOps culture is obvious, so extract the advantage of DevOps methodologies to your
current software development and IT Operation.
● The cultural transition can not happen without help for top-level management, but starting the
implementation of DevOps at the internal team level or start with small is a beneficial opportunity to
discover how the DevOps culture can improve many areas within the organization.
● In a limited scale, teams will showcase what DevOps should accomplish, find and knockdown bottlenecks
when the problems are still manageable enough to solve quickly.
● Successful transformations are mostly progressive journeys rather than "big bang" transformation.
28.
29.
30. Addition Information / Reading Material
• DevOps4Me – by Najib Radzuan
• All about DevOps, DevSecOps, Tutorial, Study Guide for certifications.
• https://blog.devops4me.com
• DevOps Malaysia Meetup (https://www.meetup.com/DevOpsMalaysia/)
• Monthly meetup(online & Onsite conference), DevOps community for MY.
• Slack Channel -> http://engineers.my
• DevOps.com (https://devops.com/)
• Latest News, Technology, Trending on DevOps
• DevOps Institute ( https://devopsinstitute.com/ )
• DevOps Global community, they always promote DevOps culture and have annual State of
DevOps Report.
• SKILup a community-based initiative by DevOps Institute, are the global series of know-how
meetups which are advancing the Humans of DevOps
• Upskill, Blog, Certification for DevOps related.