1
00:00:02,250 --> 00:00:04,939
So, this Do-it-Yourself approach

2
00:00:04,939 --> 00:00:08,740
has a couple of potential downsize at least.

3
00:00:08,740 --> 00:00:12,830
And that is what I meant when I mentioned trade-offs

4
00:00:12,830 --> 00:00:15,000
at the beginning of this module.

5
00:00:15,000 --> 00:00:18,807
Sometimes you have to choose whether you want full control

6
00:00:18,807 --> 00:00:22,060
and also the responsibility that comes with it

7
00:00:22,060 --> 00:00:25,620
or if you are fine with less control

8
00:00:25,620 --> 00:00:29,480
because you'll have the benefit of less responsibility.

9
00:00:29,480 --> 00:00:31,700
And in this concrete scenario,

10
00:00:31,700 --> 00:00:33,360
this could mean that we switch away

11
00:00:33,360 --> 00:00:37,020
from this totally self-managed service

12
00:00:37,020 --> 00:00:39,900
or this self-managed remote host

13
00:00:39,900 --> 00:00:43,913
to a third party managed solution.

14
00:00:44,890 --> 00:00:48,250
So instead of running our own machines, for example,

15
00:00:48,250 --> 00:00:50,340
running our own EC2 instances,

16
00:00:50,340 --> 00:00:52,690
we might wanna use a managed service.

17
00:00:52,690 --> 00:00:54,470
Because as I mentioned already

18
00:00:54,470 --> 00:00:58,390
for our own machines, our own remote hosts,

19
00:00:58,390 --> 00:01:01,440
we have to create and manage them ourselves.

20
00:01:01,440 --> 00:01:03,050
We have to keep them updated

21
00:01:03,050 --> 00:01:07,670
and possibly also monitor and scale them ourselves.

22
00:01:07,670 --> 00:01:11,410
If our application grows and we get more incoming traffic,

23
00:01:11,410 --> 00:01:13,090
we have to ensure on our own

24
00:01:13,090 --> 00:01:15,790
that we somehow deal with that traffic

25
00:01:15,790 --> 00:01:19,730
and we ensure that our application doesn't go down.

26
00:01:19,730 --> 00:01:21,240
Now, don't get me wrong,

27
00:01:21,240 --> 00:01:22,900
this is not always bad.

28
00:01:22,900 --> 00:01:25,360
It's great if you have that knowledge,

29
00:01:25,360 --> 00:01:29,450
if you are an experienced administrator and cloud expert,

30
00:01:29,450 --> 00:01:30,500
but if you're not,

31
00:01:30,500 --> 00:01:34,060
you risk running a setup which might be unstable

32
00:01:34,060 --> 00:01:36,690
and maybe also insecure.

33
00:01:36,690 --> 00:01:40,910
And that's why we might go for a managed service,

34
00:01:40,910 --> 00:01:45,290
for managed remote hosts or machines as I like to call them

35
00:01:45,290 --> 00:01:50,290
and here AWS ECS could be a service that helps us.

36
00:01:50,330 --> 00:01:52,930
ECS is a service offered by Amazon

37
00:01:52,930 --> 00:01:56,030
and it stands for Elastic Container Service

38
00:01:56,030 --> 00:01:57,630
and as the name implies,

39
00:01:57,630 --> 00:02:01,120
it is a service that helps us with managing containers.

40
00:02:01,120 --> 00:02:02,730
With launching them, running them,

41
00:02:02,730 --> 00:02:04,913
monitoring them and so on.

42
00:02:05,880 --> 00:02:06,713
And again,

43
00:02:06,713 --> 00:02:08,460
just to make this clear,

44
00:02:08,460 --> 00:02:12,280
other cloud providers also have similar services.

45
00:02:12,280 --> 00:02:16,530
For example, Microsoft Azure also has container services

46
00:02:16,530 --> 00:02:19,010
which make managing containers easier

47
00:02:19,010 --> 00:02:21,480
and which take care of that heavy lifting

48
00:02:21,480 --> 00:02:23,980
and that server management for you.

49
00:02:23,980 --> 00:02:25,800
So it's not just AWS,

50
00:02:25,800 --> 00:02:29,460
I'm just picking AWS as an example here.

51
00:02:29,460 --> 00:02:32,760
Now, the advantage of using such a managed service

52
00:02:32,760 --> 00:02:35,630
is that the entire creation management,

53
00:02:35,630 --> 00:02:38,970
updating, monitoring, scaling,

54
00:02:38,970 --> 00:02:41,220
all of that is simplified

55
00:02:41,220 --> 00:02:45,200
because a third party service, in this case AWS,

56
00:02:45,200 --> 00:02:46,290
takes care about it

57
00:02:46,290 --> 00:02:48,650
and we just need to tell AWS

58
00:02:48,650 --> 00:02:51,290
how it should take care about that.

59
00:02:51,290 --> 00:02:54,880
And therefore using such a managed service is great

60
00:02:54,880 --> 00:02:57,930
if you simply want to deploy an application

61
00:02:57,930 --> 00:02:59,980
or in this case a container,

62
00:02:59,980 --> 00:03:01,700
because you then don't have to worry

63
00:03:01,700 --> 00:03:04,040
about all the detailed setup work.

64
00:03:04,040 --> 00:03:05,400
And that's what I mean.

65
00:03:05,400 --> 00:03:07,240
We have less controlled then,

66
00:03:07,240 --> 00:03:10,130
but we also have less responsibility

67
00:03:10,130 --> 00:03:13,010
and less chances of messing something up.

68
00:03:13,010 --> 00:03:16,800
However, I also wanna emphasize at this point

69
00:03:16,800 --> 00:03:19,260
that switching to some managed service,

70
00:03:19,260 --> 00:03:24,060
no matter if it's by AWS or by any other provider,

71
00:03:24,060 --> 00:03:27,780
means that you don't just use Docker anymore,

72
00:03:27,780 --> 00:03:32,570
instead, you now use a service provided by a cloud provider

73
00:03:32,570 --> 00:03:36,220
and you have to follow the rules of that service

74
00:03:36,220 --> 00:03:37,300
you could say.

75
00:03:37,300 --> 00:03:40,120
That simply means that deploying containers

76
00:03:40,120 --> 00:03:41,960
and running containers

77
00:03:41,960 --> 00:03:45,400
is now not done with the Docker command anymore

78
00:03:45,400 --> 00:03:49,160
because now we don't install Docker on some machine anymore

79
00:03:49,160 --> 00:03:52,420
that's the entire idea behind a managed service,

80
00:03:52,420 --> 00:03:55,740
but instead it means that we now will need to use the tools

81
00:03:55,740 --> 00:03:57,600
the cloud provider gives us

82
00:03:57,600 --> 00:04:00,760
for the specific service we wanna use.

83
00:04:00,760 --> 00:04:03,363
And I will show this at the example of AWS ECS.

84
00:04:06,040 --> 00:04:11,040
This Elastic Container Service by AWS in the next lectures.

85
00:04:11,590 --> 00:04:13,720
It's just one possible example

86
00:04:13,720 --> 00:04:15,980
and therefore these steps shown there

87
00:04:15,980 --> 00:04:18,579
will only work for that service.

88
00:04:18,579 --> 00:04:21,070
But of course I can't cover every service

89
00:04:21,070 --> 00:04:23,610
by every cloud provider in this course.

90
00:04:23,610 --> 00:04:26,560
also since this is not a cloud development course

91
00:04:26,560 --> 00:04:27,753
but a Docker course.

92
00:04:28,680 --> 00:04:31,730
I still wanna show you over the next lectures,

93
00:04:31,730 --> 00:04:34,030
how you could take what you learned

94
00:04:34,030 --> 00:04:37,620
and migrate that into the rule set

95
00:04:37,620 --> 00:04:41,920
a specific service gives you or forces on you

96
00:04:41,920 --> 00:04:45,140
so that you see how you still work with containers

97
00:04:45,140 --> 00:04:46,330
and images,

98
00:04:46,330 --> 00:04:48,660
but how you now use them in conjunction

99
00:04:48,660 --> 00:04:50,620
with such a managed service.

100
00:04:50,620 --> 00:04:53,330
And therefore what you'll learn over the next lectures

101
00:04:53,330 --> 00:04:57,030
will help you not just with this specific service,

102
00:04:57,030 --> 00:04:59,740
but with any service by any cloud provider

103
00:04:59,740 --> 00:05:02,900
because they all will have their own documentation,

104
00:05:02,900 --> 00:05:04,300
their own rules,

105
00:05:04,300 --> 00:05:07,830
and you need to be flexible to follow these rules.

106
00:05:07,830 --> 00:05:11,310
And you will see an example over the next lectures.

107
00:05:11,310 --> 00:05:13,740
And that again is dad's trade off.

108
00:05:13,740 --> 00:05:15,940
You can manage everything on your own.

109
00:05:15,940 --> 00:05:18,410
You can set up a remote machine on your own

110
00:05:18,410 --> 00:05:20,070
and install Docker on it

111
00:05:20,070 --> 00:05:22,900
and run all these Docker commands you already know,

112
00:05:22,900 --> 00:05:26,190
but you don't have to manage everything your on your own.

113
00:05:26,190 --> 00:05:28,330
Or you use that managed service

114
00:05:28,330 --> 00:05:30,810
as you will see it over the next lectures

115
00:05:30,810 --> 00:05:34,340
and you have to follow their rules so to say.

116
00:05:34,340 --> 00:05:36,480
Nonetheless, we'll of course still be working

117
00:05:36,480 --> 00:05:37,410
with containers

118
00:05:37,410 --> 00:05:40,090
and therefore what you'll learn about that still applies.

119
00:05:40,090 --> 00:05:41,290
That doesn't change.

120
00:05:41,290 --> 00:05:44,303
It'll just be some different commands which we execute.