1
00:00:02,110 --> 00:00:05,123
Over the last lectures we switched

2
00:00:05,123 --> 00:00:07,130
from our multi container set up

3
00:00:07,130 --> 00:00:09,990
where we had our own MongoDB container

4
00:00:09,990 --> 00:00:12,780
to this single container deployment

5
00:00:12,780 --> 00:00:15,590
where we instead utilized MongoDB Atlas

6
00:00:15,590 --> 00:00:18,984
for the database and I outlined why we did this

7
00:00:18,984 --> 00:00:21,160
in the last lectures.

8
00:00:21,160 --> 00:00:25,480
Now I wanna finalize our deployed application

9
00:00:25,480 --> 00:00:29,770
and reach the final architecture for this application.

10
00:00:29,770 --> 00:00:32,963
Because we must not forget that previously when we

11
00:00:32,963 --> 00:00:36,170
learned about Docker Compose we had a backend

12
00:00:36,170 --> 00:00:37,850
and a front end.

13
00:00:37,850 --> 00:00:40,510
And I now brought back that front end,

14
00:00:40,510 --> 00:00:43,380
you attached find this updated project

15
00:00:43,380 --> 00:00:46,180
which is the project configuration we derived

16
00:00:46,180 --> 00:00:47,340
up to this point.

17
00:00:47,340 --> 00:00:50,790
So all to the Docker Compose file without MongoDB.

18
00:00:50,790 --> 00:00:54,520
But now also again with the react front end

19
00:00:54,520 --> 00:00:56,810
which renders this website

20
00:00:56,810 --> 00:00:59,075
users will be able to interact with.

21
00:00:59,075 --> 00:01:03,144
Now our final goal here will be to stick to

22
00:01:03,144 --> 00:01:05,181
using MongoDB Atlas.

23
00:01:05,181 --> 00:01:08,061
But of course now we don't just wanna have to

24
00:01:08,061 --> 00:01:11,320
NodeJS REST API being deployed,

25
00:01:11,320 --> 00:01:15,750
but we also wanna have a second container up and running

26
00:01:15,750 --> 00:01:18,650
which holds our react single page application

27
00:01:18,650 --> 00:01:21,180
so that users can reach that.

28
00:01:21,180 --> 00:01:24,260
And then it's this single page application

29
00:01:24,260 --> 00:01:27,464
talking to our NodeJS REST API.

30
00:01:27,464 --> 00:01:31,750
And therefore I again wanna deploy a second container.

31
00:01:31,750 --> 00:01:35,040
I wanna deploy this react single page application

32
00:01:35,040 --> 00:01:39,390
to my ECS task so that we again have two containers there.

33
00:01:39,390 --> 00:01:42,083
And that's there for what we're going to tackle next.

34
00:01:42,083 --> 00:01:44,750
And it might sound very easy.

35
00:01:44,750 --> 00:01:47,500
We did deploy a couple of containers already.

36
00:01:47,500 --> 00:01:50,290
But this specific application

37
00:01:50,290 --> 00:01:54,540
and applications like this react single page application

38
00:01:54,540 --> 00:01:58,120
have their very own challenging element

39
00:01:58,120 --> 00:02:01,370
which we have to understand and solve first

40
00:02:01,370 --> 00:02:04,035
before we can deploy anything.

41
00:02:04,035 --> 00:02:07,160
And that is that this application,

42
00:02:07,160 --> 00:02:09,470
the react single page application,

43
00:02:09,470 --> 00:02:12,500
and all similar applications,

44
00:02:12,500 --> 00:02:14,483
front end web applications,

45
00:02:15,363 --> 00:02:17,060
typically have a build step.

46
00:02:17,060 --> 00:02:20,410
Which means we can't run them on the server

47
00:02:20,410 --> 00:02:22,520
as we run them locally.

48
00:02:22,520 --> 00:02:23,553
And here's why.