1
00:00:01,180 --> 00:00:03,860
Are ticket service is now mostly complete.

2
00:00:03,860 --> 00:00:08,600
We put together the implementation we got some tests and we also does a manual testing with postmen.

3
00:00:08,600 --> 00:00:10,280
So what are we going to work on next.

4
00:00:10,280 --> 00:00:15,170
Well I think there's a couple of different options available to us in total we're going to over three

5
00:00:15,170 --> 00:00:19,140
possible options on what we can work on right now and then eventually make a decision.

6
00:00:19,190 --> 00:00:24,170
So option number one I think we could definitely go over to our next J.S. client application and start

7
00:00:24,170 --> 00:00:29,300
to add in some ticket related stuff such as the ability to view tickets create them edit them and so

8
00:00:29,300 --> 00:00:32,290
on that could definitely be done.

9
00:00:32,290 --> 00:00:38,140
Another option would be to start to create our orders service as a quick reminder when the services

10
00:00:38,140 --> 00:00:43,570
inside of our project is the order service and this thing is going to hold all the information related

11
00:00:43,570 --> 00:00:48,380
to a user attempting to purchase a very particular ticket.

12
00:00:48,500 --> 00:00:50,380
Well that's definitely other option as well.

13
00:00:50,380 --> 00:00:55,840
The order service is going to at a very base level can be somewhat similar in nature to the ticket service

14
00:00:56,140 --> 00:01:00,750
where we're going to be creating updating records viewing records stuff like that.

15
00:01:00,760 --> 00:01:02,720
So fairly similar in nature.

16
00:01:02,800 --> 00:01:07,870
And then finally our last option we could start to add in some code for handling events.

17
00:01:07,900 --> 00:01:12,610
So in other words implement the event bus and we could wired up to the ticket service and get a better

18
00:01:12,610 --> 00:01:15,060
idea of how that thing works.

19
00:01:15,070 --> 00:01:16,450
So which one are we going to go with.

20
00:01:16,450 --> 00:01:20,900
Well you could probably guess by the title the section we're gonna go with option number three we're

21
00:01:20,900 --> 00:01:25,270
going to start to add in this event bus we're gonna get a better understanding of how it works and so

22
00:01:25,270 --> 00:01:25,840
on.

23
00:01:25,900 --> 00:01:31,660
The reason for this is that understanding some limitations or some properties of our event bus is going

24
00:01:31,660 --> 00:01:38,020
to be absolutely tremendous in understanding how the order service and our ticket service are going

25
00:01:38,020 --> 00:01:39,510
to work together.

26
00:01:39,550 --> 00:01:43,960
So if we take care of this stuff right now even though we're not going to be really emitting any events

27
00:01:43,960 --> 00:01:49,120
to any other services inside of our app from the ticket service just yet because we don't have any other

28
00:01:49,390 --> 00:01:53,710
services that care about these events it's still going to be really important to understand how the

29
00:01:53,710 --> 00:01:59,100
event bus behaves because it's going to really have a big impact on how we build that order service

30
00:02:00,190 --> 00:02:02,470
so the event bus in general.

31
00:02:02,470 --> 00:02:07,360
Just a quick reminder we're going to implement it with something called the Nats streaming server.

32
00:02:07,360 --> 00:02:11,980
We had previously on our last application that way smaller application we started the course with we

33
00:02:11,980 --> 00:02:17,640
had built out our event bus from scratch that was that very simple express application.

34
00:02:17,870 --> 00:02:24,660
So in the coming videos we're going to forget the off service tickets all that stuff 1 percent just

35
00:02:24,660 --> 00:02:29,880
ignore it and we're going to have a hundred percent focus on the Nats streaming server our event bus

36
00:02:30,110 --> 00:02:33,020
and we're gonna get a much better understanding of how it works.

37
00:02:33,120 --> 00:02:38,280
In particular we're going to draw some parallels and differences compared to the custom very simple

38
00:02:38,280 --> 00:02:39,930
event bus we put together earlier.

39
00:02:39,930 --> 00:02:43,250
Just help you understand how this thing really behaves.

40
00:02:43,290 --> 00:02:44,790
So that mind quick pause right here.

41
00:02:44,790 --> 00:02:49,580
Let's start to work with this Nat streaming server event bus thing in the next video.