1
00:00:00,950 --> 00:00:03,000
All right, let's start to wrap things up.

2
00:00:03,120 --> 00:00:06,450
So the first thing I wanna do is show you how to shut down that community's cluster.

3
00:00:06,470 --> 00:00:08,000
We had created on Digital Ocean.

4
00:00:08,840 --> 00:00:12,380
So when you are ready to close everything down, we're going to go back over to Digital Ocean.

5
00:00:13,390 --> 00:00:15,250
We're going to first find the networking page.

6
00:00:16,180 --> 00:00:17,830
We're going to find load balancers.

7
00:00:18,250 --> 00:00:20,500
Well, then find a load balancer, those created right here.

8
00:00:20,830 --> 00:00:22,810
We'll click on more and then you can destroy it.

9
00:00:23,230 --> 00:00:26,380
Remember, you pay about ten dollars per month for this load balancer.

10
00:00:26,710 --> 00:00:28,270
So when you're all done testing the stuff out.

11
00:00:28,510 --> 00:00:29,520
Don't forget to delete it.

12
00:00:30,860 --> 00:00:32,570
Then you also delete the communities cluster.

13
00:00:32,630 --> 00:00:33,740
We'll go to Cooper Nettie's.

14
00:00:34,280 --> 00:00:35,600
We'll find our ticketing cluster.

15
00:00:35,780 --> 00:00:37,820
Go to more and then destroy that as well.

16
00:00:38,420 --> 00:00:42,530
We are paying about 30 dollars per month for the ticketing cluster, so don't forget to destroy that

17
00:00:42,530 --> 00:00:43,230
at some point.

18
00:00:45,480 --> 00:00:45,660
All right.

19
00:00:45,690 --> 00:00:49,590
So beyond that, let's want to give you a couple of quick notes on how you might possibly expand this

20
00:00:49,590 --> 00:00:50,190
application.

21
00:00:50,730 --> 00:00:54,680
The first and probably most obvious thing we should probably add in is HTP support.

22
00:00:55,170 --> 00:00:57,870
Right now, we can only connect to our application over HTP.

23
00:00:58,950 --> 00:01:02,850
If you want to add an HDTV, yes, you can take a look at cert manager IoE.

24
00:01:04,130 --> 00:01:10,550
This is an open source library that makes it fairly easy to add in HTP s or a Cuban I.D. cluster that

25
00:01:10,550 --> 00:01:12,030
is using Ingress and Genex.

26
00:01:12,610 --> 00:01:17,720
The documentation is a little bit challenging to get through, but at the end of day, it is kind of

27
00:01:17,720 --> 00:01:21,920
a straightforward process, as straightforward as HDD is in general.

28
00:01:23,180 --> 00:01:27,340
The next thing you might try doing is adding in a new service, perhaps with email support.

29
00:01:27,940 --> 00:01:33,760
So maybe after a user purchases a order or purchases a ticket, we should send them some kind of email

30
00:01:33,790 --> 00:01:35,590
just to tell them, hey, you just paid for this thing.

31
00:01:35,590 --> 00:01:37,780
And here's some details on a ticket you just purchased.

32
00:01:38,450 --> 00:01:43,420
So we might do that by creating a new service and we might decide to use a third party e-mail provider

33
00:01:43,420 --> 00:01:46,690
such as MailChimp or sent Grid or something else like that.

34
00:01:47,530 --> 00:01:51,070
This new service can then listen for events around in order being paid for.

35
00:01:51,470 --> 00:01:55,510
And as soon as the order is paid for, the service can send off an e-mail to that particular user.

36
00:01:58,810 --> 00:02:00,950
The next thing you might add in is a build step.

37
00:02:01,250 --> 00:02:06,080
So right now, all of our services inside of our production cluster are technically running in development

38
00:02:06,080 --> 00:02:06,410
mode.

39
00:02:06,890 --> 00:02:12,620
They're using T.S.A. Dev to actually invoke the individual services or at least the back end typescript

40
00:02:12,620 --> 00:02:13,020
ones.

41
00:02:13,560 --> 00:02:16,430
And the next application is still running in dev mode as well.

42
00:02:17,180 --> 00:02:21,170
We could definitely speed up all of our different services by running them in production mode.

43
00:02:21,710 --> 00:02:26,210
To do this, we're going to create a separate docker file for each service that is going to build up

44
00:02:26,240 --> 00:02:27,890
each service in a production style.

45
00:02:28,280 --> 00:02:30,080
Really, just about the only thing that needs to change.

46
00:02:30,110 --> 00:02:34,670
You're going to add in a single command into each one to tell the application to build itself.

47
00:02:35,030 --> 00:02:38,150
In the case of next, it's something like NPM, run, build or something like that.

48
00:02:38,810 --> 00:02:43,910
And then for the actual execution command in those Docker files, you'll change it to one of the appropriate

49
00:02:43,910 --> 00:02:46,400
command is generally node index J.S..

50
00:02:48,060 --> 00:02:51,630
The last thing you might try doing, and this is really just for people who are expecting to work on

51
00:02:51,630 --> 00:02:57,090
micro services projects very quickly or very soon with teams of other engineers, it might be nice if

52
00:02:57,090 --> 00:02:58,710
we had a staging cluster.

53
00:02:59,080 --> 00:03:03,570
So staging cluster would be not a production cluster, but a cluster where other team members could

54
00:03:03,570 --> 00:03:04,710
test out our application.

55
00:03:05,550 --> 00:03:08,190
So maybe we should create a another cluster on digital ocean.

56
00:03:08,670 --> 00:03:13,620
It should use some other kind of domain name, and it should only be accessible to people who are trying

57
00:03:13,620 --> 00:03:15,270
to, well, test out the application.

58
00:03:15,930 --> 00:03:18,570
We might then create another branch on our GitHub repo.

59
00:03:19,730 --> 00:03:22,190
And try another kind of workflow scripts to it.

60
00:03:22,610 --> 00:03:28,220
We could say that whenever someone tries to push some code to this staging branch, maybe we will deploy

61
00:03:28,220 --> 00:03:30,320
the application to that staging cluster.

62
00:03:30,770 --> 00:03:35,300
And then other people could come and test out our application before we finally merge that code into

63
00:03:35,300 --> 00:03:35,720
master.

64
00:03:36,880 --> 00:03:39,520
Those are four possible ways of expanding this application.

65
00:03:39,850 --> 00:03:44,710
And, of course, the most open ended one year is really add in adding in some additional services.

66
00:03:45,040 --> 00:03:45,940
Apsley, feel free.

67
00:03:46,000 --> 00:03:50,920
You do not only have to do something around e-mail, get out in any number of other kind of services

68
00:03:50,920 --> 00:03:51,670
to our application.

69
00:03:53,110 --> 00:03:53,380
All right.

70
00:03:53,420 --> 00:03:54,310
So that is it.

71
00:03:54,550 --> 00:03:59,500
This is by far the longest course I have ever created and I really hope you enjoyed it.

72
00:03:59,860 --> 00:04:02,050
It took about two months for me to record everything.

73
00:04:02,500 --> 00:04:06,640
And I recorded, on average, about one and a half hours of video per day.

74
00:04:07,390 --> 00:04:11,950
You'll notice at the end, total doesn't really total up to two months times one point five.

75
00:04:12,610 --> 00:04:15,580
Turns out I recorded a ton of video, ended up throwing it away.

76
00:04:15,670 --> 00:04:17,470
I do that all the time for all these different courses.

77
00:04:17,850 --> 00:04:19,780
Does it really was a lot of work on my side.

78
00:04:19,810 --> 00:04:21,130
I really hope you enjoyed it.

79
00:04:21,880 --> 00:04:26,020
Put in a lot of effort and I hope that you learned a lot during this process.

80
00:04:27,020 --> 00:04:30,980
I do hope you will check out some my other courses as well in the future and in general, I hope you

81
00:04:30,980 --> 00:04:33,380
have a good time with the knowledge you gained in this course.

82
00:04:34,040 --> 00:04:34,610
That's it for me.

83
00:04:34,700 --> 00:04:35,930
And I will catch you later.