0
1
00:00:00,390 --> 00:00:03,180
And the last question you have here is that I'm at the point I'm making a decision whether or not I
1

2
00:00:03,180 --> 00:00:06,500
want to use a single notes form or just use Docker with compose.
2

3
00:00:06,510 --> 00:00:08,790
And don't worry about swarm for now.
3

4
00:00:08,820 --> 00:00:17,880
That's a great question and I have an answer for that on my AMA. So over on my AMA I think it's
4

5
00:00:17,880 --> 00:00:18,990
when my top post
5

6
00:00:24,050 --> 00:00:26,480
is should I use swarm or should I use compose.
6

7
00:00:26,630 --> 00:00:36,610
My opinion is always use swarm if it's a production machine it should always use swarm and I list all
7

8
00:00:36,610 --> 00:00:43,980
of the reasons why a single node swarm is better than compose the main main reason is that you can't
8

9
00:00:43,980 --> 00:00:49,140
do rolling updates without downtime with compose you would have to bring them all down.
9

10
00:00:49,320 --> 00:00:52,910
Change out the images and then bring up new containers right.
10

11
00:00:53,100 --> 00:00:57,900
Because composed as it had composed was never designed Docker compose the command line was never designed
11

12
00:00:57,900 --> 00:01:05,280
for production use it was never designed for the concept of always uptime or multi servers or anything
12

13
00:01:05,280 --> 00:01:06,230
like that right.
13

14
00:01:06,240 --> 00:01:11,010
It doesn't have a database running in the background it collects information and stores decisions it's
14

15
00:01:11,010 --> 00:01:12,690
making around orchestration.
15

16
00:01:12,960 --> 00:01:16,400
So that's why a single node swarm is the right way to go.
16

17
00:01:16,470 --> 00:01:19,610
And I list a bunch of reasons there you can definitely check those out.