DevOps has been such a buzzword in the IT field nowadays. If you look into job postings, you might be surprised to find terms like "work with DevOps team", "work in an agile team" etc. What is DevOps? What is agile? And why all these? 樂 Join us on 24 May 2021, where we have a short session to explore on the events that led to the trend nowadays We will be exploring on the current trends, tech stacks and the existence of DevOps itself! 朗 Mark this date on your calendar and we'll see you there! * Note: This is an introductory "brief overview" session that gives you context on our upcoming events. Slides by KwongTN.

1. Intro to DevOps
Kwong Tung Nan
Community Lead, DSC UTeM
linkedin.com/in/kwongtn/

2. Disclaimer
● Any opiniated statements in this session are of my own,
and is not related to / does not represent DSC UTeM
whatsoever.
● Content presented here are purely for educational
purposes only. You are responsible for your own
actions.

3. Web Session Housekeeping
Before we start:
⁃ Remember to always mute your microphone, unless prompted.
⁃ There will be a QnA session at the end, so please take note of your questions and
ask then – we won’t bite!
⁃ Tell us how we did in the survey at the end!

4. Web Session Housekeeping
Please be reminded that:
⁃ Today’s webinar is being recorded. We will share a link after the event is
complete.
⁃ Slides will be shared after the event.

5. Event Hashtags
#DSCUTeM / #DSC_UTeM
#GoogleDevelopers
#DeveloperStudentClubs / #DSC
#DevOps

6. Agenda
• What is the Internet? And a brief history.
• The Internet’s current trends
• Full Stack Development
• The ongoing battle between the “Production” & “Development”
Teams
• The DevOps term & the agile development cycle
• A brief idea of the DevOps series
• QnA

7. This session will be
slightly boring…
But why are we doing this? 🤔🤔

8. Some quote about importance of
understanding something philosophically
By me

9. What is the Internet?
Beep boop beep … bop beep … ?

10. A (global) bunch of devices that talk to each
other, with some infrastructure to support it.
Seriously, that’s about it.

11. The Lower Internet Hierarchy
Tier 3 Network Tier 3 Network
PSTN
PSTN
PABX Router
Ethernet
Metro-fiber
Cable
Operator
Dial-up
customer
POTS
ADSL2
DSLAM
Central Office
Cable
customer
ADSL customer
(Triple play)
ADSL
customer
Leased line
(T3/E3)
Leased line
(T1/E1)
Cable plant
ADSL
Filter
Filter
Filter
Internet

12. The Higher Internet Hierarchy
PoP #1
Tier 3 Network
(multi-homed ISP)
Tier 3 Network
(single homed ISP)
PoP #2
PoP #3
Tier 2 ISP
Tier 2 Networks
IXP
Tier 1 Networks
Peering
Transit
Transit
Transit
Transit
Internet users
(business, consumers, etc)

13. Worldwide submarine cables

14. A Brief History of the
Internet
When computers started to talk to each other

15. The origin of the Internet
Like many projects (like GPS)
●The internet started as a military / scientific project
●ARPAnet (Advanced Research Projects Agency Network)
●NSFNET (the National Science Foundation Network) was an
early open network to share data

16. Robert Elliot Kahn
a.k.a. Bob Khan, Inventor of
Internet #1
• Completed an early version of
TCP in 1973 & co-founded the
Internet Society in 1992

17. Vinton Gray Cerf
a.k.a. Vint Cerf, Inventor of
Internet #2
• Completed an early version of
TCP in 1973 & co-founded the
Internet Society in 1992

18. Sir Tim Berners-Lee
a.k.a. W3C Founter
• Proposed an Information
Management System on 12
March 1989
Implemented it on Mid-Nov

19. DevOps, why? From multiple perspectives
Data
Consumption
Adoption
Rate
Funding /
Earnings
Team
Priorities

20. Current Trends
(also known as “Problem Statement #1”)

21. The increase of adoption rate

22. More and more people are using the Internet…
Source: domo.com

23. …especially during the pandemic

24. In 2020…
Every minute..
• 500 hours of content to
YouTube
• $ 1M USD spent online
• 347k stories on Instagram
• 147k pictures to Facebook
Source: domo.com

25. Every day..

26. All these stored in..

27. To put it into perspective…
Source:
◄ SIZE of INTERNET ► BYTES in perspective 🌐🌐 by
Alvaro Gracia Montoya - MetaBallStudios
2016

28. With great earnings.. Comes great
investment
Source: visualcapitalist.com

29. Fun fact:
Source:
The Two High-Growth Sectors That Could Outperform Tech
[visualcapitalist.com]

31. What can we conclude from these?
●Data consumption & creation is growing at an exponential rate.
●Organizations must be quick to deploy solutions, or risk getting replaced by
competitors.
●You must fail fast, fail more and recover fast.
●Data is the new gold.
●More and more money is being pumped into the tech sector.

32. Full Stack Development
What do we mean when we say “Full Stack”?
And also.. “Problem Statement #2”

33. Architecture Separation

34. From frontend to backend and beyond*
* Depending on salary

35. “Operations” vs
“Development” Teams
And the bad blood between them
And “Problem Statement #3”

36. A typical IT department

37. The Bad Blood

38. How Dev sees Ops

39. What does operations do?
Architectural Engineering
8%
Deployment Management
31%
Incident Management
20%
Problem Engineering
10%
Overhead
11%
Requests
6%
Software Development
7%
Site Management
7%
Source:
Study from Deepak Patil [Microsoft
Global Foundation Services], 2006

40. How Ops sees Dev

41. What happens when change is required?
Operations
Development
Architecture
Quality
Assurance
(QA)
Boss

42. The old and hard “waterfall model”

43. In short, Dev vs Ops ‘s Priority:
Developers
●Maximize change (get products to
market as soon as possible)
●Deploy code everywhere
●Use the latest and shiniest technology
●Freedom!!
●Uses the “development” / “R&D” budget
●Optimize for stability (the less change
the better!)
●Set Control & Standards
●Less regulatory pressure
●Reduce surprises
●Uses the “run” / “operations” budget
Operation

44. The Advent of
DevOps
And how the “agile” movement started

45. DevOps is a methodology that help both
developers and operators reach their
goals while maximizing quality & value
delivery to the users.
TLDR: Maximize value delivery in a short time, while
maintaining quality

46. Essential Principles of DevOps
1. Infrastructure as Code (IaC)
2. Continuous Integration / Delivery (CI/CD)
3. Culture of Collaboration

47. Infrastructure as Code (IaC)
Issues at hand
●Humans make mistakes
●The more the commands, the higher the rate of failure

48. {
"Parameters": {
"RootDomainName": {
"Description": "Domain name for your website (example.com)",
"Type": "String"
}
},
"Resources": {
"RootBucket": {
"Type": "AWS::S3::Bucket",
"Properties": {
"BucketName" : {"Ref":"RootDomainName"},
"AccessControl": "PublicRead",
"WebsiteConfiguration": {
"IndexDocument":"index.html",
"ErrorDocument":"404.html"
}...
IaC Example

49. Infrastructure as Code (IaC)
●Automate provisioning
●Speed up deployments
●Make them repeatable & reliable
●Make sure standards are respected
●Time to Recovery
●Allow Devs to do tasks themselves!

50. Continuous Integration / Delivery (CI/CD)
Key Ideas. The more you deploy:
●The more you master the art of deployment
●The smaller the changeset
●The better the Time to Repair / Resolution (TTR)

51. If it hurts, do it more often !
The DevOps credo

52. Zero Downtime Deployments
Get feedback while maintaining continuity
1. Feature Flipping
2. Dark Launch
3. Blue / Green Deployments
4. Canary Release

53. CI Sample

54. CD Sample

55. DevOps - You build it, you run it.
Werner Vogel, CTO @ Amazon, 2014

56. Collaboration

57. Collaboration
Change in
methodology

58. Working together

59. Dev…Sec…Ops (?)
When integrating security into your workflow
becomes too important

60. “Sec” in DevSecOps
Very briefly

61. “Sec” in DevSecOps
A real-world sample – GitHub Actions
Source: https://github.com/johannesjo/super-productivity/

62. The Future (?)

63. A Little Conclusion….
Phew! So much information to process in a day!

64. Takeaway Points
●DevOps is a methodology
●The Internet is growing bigger by the second, taking data consumption with it
●The industry needs to grow fast to stay relevant. To do that, they need to fail
more, fail fast.
●Dev and Ops need to work together
●Humans are prone to error, remove them as much as possible.

65. The DevOps Series
By DSC UTeM

66. What we will be covering
We aim to make this a bi/tri-weekly event
Session 1: Intro to DevOps & the DevOps Series
Session 2: Git, GitHub & GitKraken
Session 3: Virtualization & Hypervisors
Session 4: Containerization, Orchestration & CI/CD
Session 5: The Cloud, Serverless & Everything as a Service
Session 6: Open Source & the end of DevOps Series

68. What this series…
Will not be
●A step-by-step tutorial on how to
create your next million-dollar
application
●A high-level overview of the
technology involved
Will be

69. Some PSAs
PSA = Public Service Announcements 😉😉

70. Google Taiwan is hiring interns!
No, they don’t ask brain teasers anymore
Full-Time (for graduated/graduating students):
• Software Engineer, University Graduate, 2021
• Silicon Engineer, University Graduate, 2021
https://careers.google.com/

71. Follow us!
facebook.com/dsc.utem instagram.com/dsc.utem linkedin.com/company/
dsc-utem

72. Join the discussion too!
DSC UTeM
facebook.com/groups/762630651223921
DSC UTeM
discord.gg/tnv4U6R

73. QnA
10 mins, then group photo, then extended QnA

74. Audience Q&A Session
ⓘ Start presenting to display the audience questions on this slide.

75. Event feedback
https://forms.gle/1vD4rrPBLEb3q3rb9

76. Main reference:
●DEVOPS EXPLAINED by Jaview Baiges
https://www.devops.ch/2017/05/10/devops-explained/

77. Thank You!
Feedback form:
https://forms.gle/1vD4rrPBLEb3q3rb9