1
00:00:07,643 --> 00:00:09,840
After watching this video, you will be able to:

2
00:00:09,840 --> 00:00:11,640
Describe how applications evolved to give

3
00:00:11,640 --> 00:00:15,330
rise to DevOps,
list the three dimensions of DevOps,

4
00:00:15,330 --> 00:00:19,320
and describe some essential characteristics
of DevOps.

5
00:00:19,320 --> 00:00:21,930
Let's not lose sight of the goal.

6
00:00:21,930 --> 00:00:23,550
What is the goal?

7
00:00:23,550 --> 00:00:25,210
Agility is the goal.

8
00:00:25,210 --> 00:00:27,650
You want to be doing smart experimentation.

9
00:00:27,650 --> 00:00:31,859
You want to be moving in market with maximum
velocity and minimum risk.

10
00:00:31,859 --> 00:00:37,719
This way you can gain quick, valuable insights
to consistently change the value proposition

11
00:00:37,719 --> 00:00:41,649
and the quality that you deliver to your customers.

12
00:00:41,649 --> 00:00:44,230
There are three pillars for agility.

13
00:00:44,230 --> 00:00:45,949
One of the pillars is DevOps.

14
00:00:45,949 --> 00:00:52,440
This includes cultural change, automated pipelines,
infrastructure as code, and immutable infrastructure.

15
00:00:52,440 --> 00:00:56,899
The second pillar is microservices and includes
a loosely coupled application design using

16
00:00:56,899 --> 00:01:00,629
microservices that communicate via REST APIs.

17
00:01:00,629 --> 00:01:04,940
Microservices are designed to resist failure
and tested by breaking them and failing

18
00:01:04,940 --> 00:01:05,940
fast.

19
00:01:05,940 --> 00:01:08,550
The third pillar is containers.

20
00:01:08,550 --> 00:01:13,330
Containers are developer-centric environments
that give us portability and fast startup.

21
00:01:13,330 --> 00:01:18,770
They also enable an ecosystem that allows
quick deploys with immutable infrastructure.

22
00:01:18,770 --> 00:01:21,340
I like to call this the perfect storm.

23
00:01:21,340 --> 00:01:27,170
Taken separately, these are impressive technologies
on their own, but together they enable powerful

24
00:01:27,170 --> 00:01:28,170
change.

25
00:01:28,170 --> 00:01:33,900
You have DevOps for speed and agility, microservices
for small deploys, and containers for ephemeral

26
00:01:33,900 --> 00:01:36,300
run times with fast startup.

27
00:01:36,300 --> 00:01:38,310
Ephemeral means lasting for a very short time.

28
00:01:38,310 --> 00:01:42,570
They are ephemeral because when a container
goes bad, we don't try to fix it.

29
00:01:42,570 --> 00:01:44,640
We just delete it and replace it with a new
one.

30
00:01:44,640 --> 00:01:47,840
These are throw-away runtimes.

31
00:01:47,840 --> 00:01:51,710
Tony Stafford says, “DevOps starts with
learning how to work differently.

32
00:01:51,710 --> 00:01:56,780
It embraces cross-functional teams with openness,
transparency, and respect as pillars.”

33
00:01:56,780 --> 00:01:57,780
That's a tall order.

34
00:01:57,780 --> 00:02:01,600
Does your organization embrace openness, transparency,
and respect?

35
00:02:01,600 --> 00:02:05,490
That is what's required to become DevOps.

36
00:02:05,490 --> 00:02:08,679
Let's talk about application evolution for
a moment.

37
00:02:08,679 --> 00:02:14,560
In the past, there was Waterfall, with its
monolithic applications deployed on physical

38
00:02:14,560 --> 00:02:15,560
servers.

39
00:02:15,560 --> 00:02:20,700
And then, at some point in time, we migrated to
Agile and used Service Oriented Architectures

40
00:02:20,700 --> 00:02:22,660
and virtual machines.

41
00:02:22,660 --> 00:02:24,660
And then, DevOps followed.

42
00:02:24,660 --> 00:02:28,130
Now we are using microservices deployed in
immutable containers.

43
00:02:28,130 --> 00:02:30,500
This has been an incremental evolution.

44
00:02:30,500 --> 00:02:32,660
We broke the monoliths into services.

45
00:02:32,660 --> 00:02:36,480
The services were still large, using Service
Oriented Architecture, but we had embraced

46
00:02:36,480 --> 00:02:38,980
services as a design concept.

47
00:02:38,980 --> 00:02:41,510
Then we had virtualization and the Cloud.

48
00:02:41,510 --> 00:02:43,140
This made things much smaller.

49
00:02:43,140 --> 00:02:49,060
With DevOps, we have evolved again into microservices
and containers to deploy them in.

50
00:02:49,060 --> 00:02:55,010
DevOps has three dimensions: culture, method,
and tools.

51
00:02:55,010 --> 00:02:57,620
Most companies focus on the tools.

52
00:02:57,620 --> 00:03:02,069
Most vendors focus on the tools as well because
that's all they can sell.

53
00:03:02,069 --> 00:03:05,540
Some companies also focus on the methods,
which are important.

54
00:03:05,540 --> 00:03:11,050
But the most important thing to focus
on is culture!

55
00:03:11,050 --> 00:03:15,950
Atlassian says, “Culture is the number-one
success factor in DevOps.

56
00:03:15,950 --> 00:03:21,610
Building a culture of shared responsibility,
transparency, and faster feedback is the foundation

57
00:03:21,610 --> 00:03:24,970
of every high-performing DevOps team.”

58
00:03:24,970 --> 00:03:30,840
If you want to be a high-performing DevOps
organization, you need to change your culture.

59
00:03:30,840 --> 00:03:39,140
While tools and methods are important… it
is culture that has the biggest impact.

60
00:03:39,140 --> 00:03:41,370
How do you change a culture?

61
00:03:41,370 --> 00:03:43,260
Culture is ingrained within us.

62
00:03:43,260 --> 00:03:44,930
It defines who we are.

63
00:03:44,930 --> 00:03:49,170
It includes elements such as our language,
our food, our values, and our stories.

64
00:03:49,768 --> 00:03:52,430
It is extremely hard to change a culture.

65
00:03:52,430 --> 00:03:54,260
Countries have cultures.

66
00:03:54,260 --> 00:03:55,640
Companies have cultures.

67
00:03:55,640 --> 00:04:01,280
Many companies attempt to become DevOps but
fail to change their culture.

68
00:04:01,280 --> 00:04:06,569
This change must come down from the top and
be embraced from the bottom up, in order for

69
00:04:06,569 --> 00:04:07,920
the change to happen.

70
00:04:07,920 --> 00:04:11,860
This is not an easy thing to do.

71
00:04:11,860 --> 00:04:13,420
How do you change a culture?

72
00:04:13,420 --> 00:04:14,940
You must change the way people think.

73
00:04:14,940 --> 00:04:16,799
They have to start thinking differently.

74
00:04:16,799 --> 00:04:20,452
You need to think about social coding and
sharing.

75
00:04:21,098 --> 00:04:23,060
You have to change the way they work.

76
00:04:23,060 --> 00:04:25,080
They need to start working differently.

77
00:04:25,080 --> 00:04:29,171
Working in small batches and using test-driven
and behavior-driven development.

78
00:04:30,522 --> 00:04:33,490
You must change the way you are organized.

79
00:04:33,490 --> 00:04:36,110
This is a lot of companies don't get this.

80
00:04:36,110 --> 00:04:41,259
You must organize differently because the
organization has a direct impact on how you

81
00:04:41,259 --> 00:04:43,800
build things.

82
00:04:43,800 --> 00:04:47,229
Most of all, you must change the way people
are measured.

83
00:04:47,229 --> 00:04:53,490
You must change your measurement system and
measure differently because you always get

84
00:04:53,490 --> 00:04:55,180
what you measure.

85
00:04:55,180 --> 00:05:02,220
In the remainder of this course, we are going
to explore the DevOps way of thinking, working,

86
00:05:02,220 --> 00:05:05,770
organizing, and measuring.

87
00:05:05,770 --> 00:05:09,990
In this video, you learned that:
Applications evolved from Waterfall development

88
00:05:09,990 --> 00:05:13,410
of monoliths to Agile development of microservices.

89
00:05:13,410 --> 00:05:17,819
DevOps has three dimensions: culture, method,
and tools.

90
00:05:17,819 --> 00:05:23,139
And the essential characteristics of DevOps
include cultural change, automated pipelines,

91
00:05:23,139 --> 00:05:27,934
infrastructure as code, microservices, containers,
and immutable infrastructure.