You are on page 1of 60

DevOps In The Real World

Khanh Le, Oct 2021


Agenda

● The evolution of Software Deployment


● What is DevOps?
● DevOps in the real world
● What should be learned?
● The key competencies

2
The evolution
of
software deployment

3
All On Personal Computer

4
Client - Server

Overload

5
Multi-Servers & Multi-Apps

6
Wasting
Resource

7
Virtualized Deployment

8
Container Deployment

9
Kubernetes

10
Example: Selenium Grid on Kubernetes.
11
Cloud

IBM Public Cloud Architecture 12


OpenStack Cloud Architecture 13
AWS Global Infrastructure

25 Launched Regions
Each with multiple Availability
Zones (AZ’s)
81 Availability Zones
11 Local Zones

17 Wavelength Zones

For ultralow latency applications


8 Announced Regions

6 Announced Local Zones


2x More Regions
With multiple AZ’s than the next
largest cloud provider
245 Countries and Territories
Served
108 Direct Connect Locations
275+ Points of Presence
265+ Edge Locations and 13
Regional Edge Caches
14
Infrastructure As Code

15
What is DevOps?

16
DevOps Model

17
How DevOps Works

Security
informationIT
Software
QualityOperations
Development
assurance

18
Benefits of DevOps

Speed Scale

Rapid Delivery
Improved Collaboration

Reliability
Security

19
DevOps
In The Real World

20
Overview

A delivery pipeline
21
Continuous delivery

22
DevOps for Web

23
An example for Web Delivery pipeline
Challenges

● Backend and front end often separated from each other. We have to make sure they are in
sync for each deployment.
● For the large system, we split it into microservices. Keeping the microservices in sync is also
challenge.

24
DevOps for Mobile

An example for Mobile App Delivery pipeline 25


Challenges

● Multi-platform support
● Mobile apps as an enterprise front end
● Speed of delivery and cycle time
● The app store
● "Pull” not “push” deployment
● Long-term impact of negative ratings

Culture and Teams

● Collaboration across mobile and back-end teams


● Learning agility from mobile app teams

26
DevOps for IoT

Application delivery handoff to engineering 27


Continuous integration and testing

● These progress as in traditional software delivery.


● The availability of simulators or device prototypes that resemble the final device as much as
possible.
● The development cycles of the firmware and hardware need to be better synchronized.

Continuous integration and testing

● Once in production, even connected devices may not be in a state to be updated when an update is
made available.
● This behavior may necessitate that firmware updates be done only when the device is idle and not
in a state that needs to be maintained (for example, a suspended state).
● They may only have a “pull” mode of receiving updates, rather than a “push” mode, which
necessitates that the user initiate the update process.

28
Hardware design for CD

● Two layers of firmware:


○ A core operational firmware (an OS), which operates the device and is infrequently
updated;
○ And the app, which provides specific features and services to the user and is more
frequently updated.

Teaming and culture

● The alignment between the hardware and firmware teams during the development
stage of the device is essential.

29
DevOps for Big Data & Analytic

30
31
An example of serverless data architecture
Challenges

● Complexity
● Skillset
● Technology maturity
● Security

32
What should be learned?
34
35
A few Knowledge
and DevOps Tools
37
Is it an job or a skill?
Yes, there is a job position called DevOps

It is also a Skill

Who need it?

❖ Developer
❖ Automation Testing Engineer
❖ DevOps Engineer
❖ Architecture Engineer
❖ Chief Technology Officer

39
Key Competencies
Cooperation
Listening
Cognitive
Problem analysis
Adaptability
Self-development
Persuasiveness
Stress resistance
Coaching
Managing conflict
Judgement
Motivating
Leadership
Delegating
Planning
Organizing
Vision
Reference

[1] The Kubernetes Authors, Kubernetes Documentation, https://kubernetes.io/docs/home/


[2] Docker, Docker Official Document, https://docs.docker.com/
[3] Software Freedom Conservancy, Selenium Grid, https://www.selenium.dev/documentation/grid/
[4] Amazon, AWS Document, https://docs.aws.amazon.com/index.html?nc2=h_ql_doc
[5] Amazon, AWS Lake Formation,
https://aws.amazon.com/lake-formation/?whats-new-cards.sort-by=item.additionalFields.postDateTime&whats
-new-cards.sort-order=desc
[6] Sanjeev Sharma, The DevOps Adoption Playbook, John Wiley & Sons, Inc., 2017
[7] Microsoft, Azure documentation, https://docs.microsoft.com/en-us/azure
[8] Le Van Khanh, The road of programer, https://www.youtube.com/watch?v=lY6YkqfApQI
[9] IBM, IBM Architecture Center, https://www.ibm.com/cloud/architecture

58
Q&A

59
Thank you!
If you have any questions, please contact Le Van Khanh
at khanh.le@paradox.ai

You might also like