1 00:00:02,180 --> 00:00:04,920 Now this is already it for this module 2 00:00:04,920 --> 00:00:09,240 which was about container communication and networks. 3 00:00:09,240 --> 00:00:13,479 Now there is more you could do to optimize this application 4 00:00:13,479 --> 00:00:16,970 and improve how containers are started. 5 00:00:16,970 --> 00:00:19,680 For example, for the moment we always lose 6 00:00:19,680 --> 00:00:24,250 all the database data whenever we stop the mongoDB database. 7 00:00:24,250 --> 00:00:27,380 This is something we could solve with volumes 8 00:00:27,380 --> 00:00:30,910 and it actually is something we will solve with volumes. 9 00:00:30,910 --> 00:00:32,770 But we'll take a look at that, 10 00:00:32,770 --> 00:00:34,840 combined with a couple of other things 11 00:00:34,840 --> 00:00:37,682 in the next module when we will dive deeper 12 00:00:37,682 --> 00:00:41,460 into building multi-container applications 13 00:00:41,460 --> 00:00:46,070 because most applications are multi-container applications. 14 00:00:46,070 --> 00:00:47,930 So we'll take a close look at that 15 00:00:47,930 --> 00:00:49,380 in the next module. 16 00:00:49,380 --> 00:00:53,070 For this module it's important that you understand 17 00:00:53,070 --> 00:00:56,040 that requests to web servers 18 00:00:56,040 --> 00:00:56,873 and so on 19 00:00:56,873 --> 00:00:59,630 are always possible in containers. 20 00:00:59,630 --> 00:01:03,430 Requests to the local host machines are easy to do 21 00:01:03,430 --> 00:01:08,430 with that host.docker.internal domain here 22 00:01:08,890 --> 00:01:12,430 and that cross container requests are easy 23 00:01:12,430 --> 00:01:13,980 if you look up the IP 24 00:01:13,980 --> 00:01:17,540 or even better if you create a network 25 00:01:17,540 --> 00:01:19,860 and then you just use the container name 26 00:01:19,860 --> 00:01:22,210 and let docker do the handwork . 27 00:01:22,210 --> 00:01:24,773 That's what you should take away from this module.