0:00 All right, so before we start building our 0:02 application, I've generated this system 0:04 architecture diagram to go over what our 0:08 architecture looks like for our application, given that it is a 0:12 fairly advanced application and we have a lot of components at play 0:15 here. 0:15 So let's start from the beginning and break down the diagram here. 0:19 So at the beginning here, we have an actor or a user that 0:23 is going to 0:23 interact with our application. Now, the first step for them is to 0:27 interact with the load balancer that's going to be accepting traffic and 0:31 forwarding on to our application. 0:33 So this load balancer and all the components inside of it will 0:36 ultimately 0:37 live inside of a Kubernetes cluster when we deploy the application. 0:41 However, locally, this will just be on our local file system 0:44 and the load 0:45 balancer, well, that's just gonna be our machine. 0:47 So the network request will come into the load balancer or our 0:51 network interface card, and then from there, 0:53 we're gonna go ahead and 0:54 expose a GraphQL server over our two first 0:58 applications here. And so these are NestJS microservices, and 1:02 importantly, they're gonna be hybrid microservice 1:05 applications. 1:06 Now, the reason why I say this is because, well, like I just said, we have the 1:10 GraphQL server that's exposed on each one. 1:13 So to do this, we have an HTTP port that's exposed on 1:16 each of these 1:17 microservices, and that's how we can send traffic over 1:19 GraphQL, and we have 1:20 that GraphQL playground where a user can actually send requests to. 1:24 And of course, this is happening over GraphQL over 1:28 HTTP. And so we have one port here. Next up, though, you can see we 1:32 actually have this line going from the jobs microservice 1:36 to the auth microservice, and that's using gRPC. 1:39 And that's why I say this is a hybrid microservice application
The rest of the transcript is for members.
Sign in 