WEBVTT - This file was automatically generated by VIMEO

0
00:00:08.500 --> 00:00:11.400
Hello and welcome to overview of devops and

1
00:00:11.400 --> 00:00:14.700
 cloud computing in this section. We will cover some devops basics

2
00:00:14.700 --> 00:00:17.800
 in cloud computing. You will learn about devops terminologies

3
00:00:17.800 --> 00:00:20.200
 principles and tooling you will

4
00:00:20.200 --> 00:00:23.900
 also be introduced to the concepts around containers and container orchestrators.

5
00:00:23.900 --> 00:00:26.500
 Finally. We will explore Cloud Computing

6
00:00:26.500 --> 00:00:28.600
 Services and deployment models.

7
00:00:30.400 --> 00:00:33.100
In this first video of section 2 we will go over

8
00:00:33.100 --> 00:00:35.900
 what devops is and why you should be practicing it.

9
00:00:36.700 --> 00:00:39.200
Devops may be one of the most misunderstood words

10
00:00:39.200 --> 00:00:42.600
 in Tech. In fact, if you read 50 blogs or watch

11
00:00:42.600 --> 00:00:45.600
 50 videos, you will most likely get 50 different definitions.

12
00:00:45.600 --> 00:00:48.200
 The confusion is in part because devops is

13
00:00:48.200 --> 00:00:51.200
 not a tool or definitive guide but a set

14
00:00:51.200 --> 00:00:54.200
 of guidelines and a philosophy that most people interpret and Implement

15
00:00:54.200 --> 00:00:54.800
 differently.

16
00:00:55.400 --> 00:00:58.300
To understand what devops is we must first travel

17
00:00:58.300 --> 00:01:01.300
 back a little bit and talk about how software used to be delivered.

18
00:01:02.700 --> 00:01:05.600
In ancient times software delivery is

19
00:01:05.600 --> 00:01:08.500
 done by two separate teams developers and operations.

20
00:01:08.500 --> 00:01:11.900
 Once the application was deemed code complete. It

21
00:01:11.900 --> 00:01:14.100
 was handed over the wall to the operations team to

22
00:01:14.100 --> 00:01:17.400
 be deployed and monitored. This was called the waterfall method.

23
00:01:18.500 --> 00:01:21.400
as you may have imagined software Engineers knew

24
00:01:21.400 --> 00:01:24.700
 very little about deploying and monitoring applications and operations

25
00:01:24.700 --> 00:01:27.300
 new next to nothing about how the software was built

26
00:01:27.300 --> 00:01:27.800
 and designed

27
00:01:28.600 --> 00:01:31.500
this caused a rift between the two camps because both sides had

28
00:01:31.500 --> 00:01:33.200
 different goals and success criteria.

29
00:01:34.100 --> 00:01:38.300
Software Engineers had to ship code no matter the cost operations had

30
00:01:38.300 --> 00:01:41.600
 to keep the software stable no matter the situation. These two

31
00:01:41.600 --> 00:01:42.800
 goals are competing.

32
00:01:45.200 --> 00:01:45.300
So

33
00:01:46.200 --> 00:01:49.300
We know how things used to be. But where does devops come

34
00:01:49.300 --> 00:01:49.400
 from?

35
00:01:50.200 --> 00:01:54.100
The term devops is a mashup of two words development and

36
00:01:53.100 --> 00:01:54.600
 operations.

37
00:01:55.300 --> 00:01:58.200
According to all accounts, the name was first uttered by

38
00:01:58.200 --> 00:02:00.300
 Patrick Dubois in 2009.

39
00:02:01.200 --> 00:02:04.300
However, the idea and methods of devops were borrowed from

40
00:02:04.300 --> 00:02:07.600
 lean manufacturing where companies like Toyota have been pioneers.

41
00:02:08.700 --> 00:02:11.200
Devopsis practice in many companies and is

42
00:02:11.200 --> 00:02:12.600
 the preferred way to ship software.

43
00:02:13.400 --> 00:02:15.300
Let's learn more about its core pillars next.

44
00:02:17.300 --> 00:02:20.700
In devops, there are three main Concepts cleverly named

45
00:02:20.700 --> 00:02:23.600
 the three ways these three ways frame the processes

46
00:02:23.600 --> 00:02:26.000
 practices and procedures used in devops.

47
00:02:26.800 --> 00:02:30.200
The first way is systems and flow work should

48
00:02:29.200 --> 00:02:32.100
 flow from left to right in One Direction

49
00:02:32.100 --> 00:02:34.000
 and not bounce back and forth.

50
00:02:34.600 --> 00:02:38.400
When we speak a flow, we mean the process of planning coding

51
00:02:37.400 --> 00:02:40.700
 testing and deploying software

52
00:02:40.700 --> 00:02:41.400
 infrastructure.

53
00:02:42.300 --> 00:02:45.200
Another way to think about this is the left usually means

54
00:02:45.200 --> 00:02:48.100
 development while the right usually means production.

55
00:02:49.400 --> 00:02:50.900
The second way is feedback.

56
00:02:51.700 --> 00:02:54.300
This is the process of passing information from right

57
00:02:54.300 --> 00:02:56.500
 to left this time as fast as you can.

58
00:02:57.400 --> 00:03:00.100
As bugs are found you need to consistent way to get

59
00:03:00.100 --> 00:03:01.400
 that data back to planning.

60
00:03:02.300 --> 00:03:05.600
Tight feedback loops enable timely iteration on software and

61
00:03:05.600 --> 00:03:07.800
 allow for correction and early detection.

62
00:03:09.100 --> 00:03:11.900
The Third Way is continuous experimentation and learning.

63
00:03:12.700 --> 00:03:15.500
Every day, you must take risk in continuously prove

64
00:03:15.500 --> 00:03:16.700
 your process and software.

65
00:03:17.300 --> 00:03:20.200
Practice makes perfect, and we learn more by failure than we

66
00:03:20.200 --> 00:03:20.800
 do success.

67
00:03:21.800 --> 00:03:24.200
In my experience doing devops correctly

68
00:03:24.200 --> 00:03:27.300
 is not the end goal or even feasible. The three ways

69
00:03:27.300 --> 00:03:30.600
 are high level Concepts in which you build from not every

70
00:03:30.600 --> 00:03:33.600
 organization will be able to follow these pillars. Exactly and that's

71
00:03:33.600 --> 00:03:36.600
 okay. We'll expand on these pillows more

72
00:03:36.600 --> 00:03:39.200
 when we discuss devops principles in a later video.

73
00:03:41.200 --> 00:03:44.100
There are many reasons why you want to practice DeVos but

74
00:03:44.100 --> 00:03:47.300
 I feel these three of the most beneficial they are technical

75
00:03:47.300 --> 00:03:50.000
 cultural and improvements to your business.

76
00:03:51.100 --> 00:03:54.200
Technical changes will reduce complexity help you deliver

77
00:03:54.200 --> 00:03:57.400
 software continuously and reduce recovery time and production.

78
00:03:58.400 --> 00:04:01.300
Culturally DeVos promotes productive teams because

79
00:04:01.300 --> 00:04:05.200
 of collaboration shared goals and Trust finally

80
00:04:04.200 --> 00:04:07.300
 business improvements occur, when there

81
00:04:07.300 --> 00:04:10.300
 are less bugs shared goals and objectives between the

82
00:04:10.300 --> 00:04:13.900
 team when everyone is striving for the same outcome. This

83
00:04:13.900 --> 00:04:16.700
 usually leads to happier employees and customers

84
00:04:18.300 --> 00:04:21.400
in this video you learn that devops is a partnership between

85
00:04:21.400 --> 00:04:24.000
 software engineering and Systems Operations.

86
00:04:24.900 --> 00:04:27.500
You also learned why devops is the evolution to

87
00:04:27.500 --> 00:04:30.500
 waterfall and is the preferred way of delivering software today.

88
00:04:31.900 --> 00:04:34.200
Finally you learn that devops not

89
00:04:34.200 --> 00:04:37.600
 only provides faster time to Market, but it can also produce fewer

90
00:04:37.600 --> 00:04:39.700
 bugs because of flow and feedback loops.

91
00:04:41.600 --> 00:04:44.500
In the next video, you will learn about DeVos principles

92
00:04:44.500 --> 00:04:46.600
 and how they can guide you. See you soon.
