An instructor explains a system architecture diagram detailing the interaction between various microservices, including authentication, reservations, payments, and notifications. The overview highlights how users interact with these services via JWTs, MongoDB databases, and third-party APIs like Stripe and Gmail.
Length 3:31
Captions English (Generated), Spanish (Auto-translated), French (Auto-translated), Korean (Auto-translated), Portuguese (Auto-translated), Vietnamese (Auto-translated) #architecture #microservices #diagram #authentication #jwt #mongodb #reservation #payments #notifications #software
0:01 In this lecture, we're gonna review a system diagram that 0:05 outlines the architecture of our application. 0:09 Now, this lecture is completely optional. 0:11 You don't need to complete this to move on with the project. 0:14 So if you simply just wanna download this and move along, you 0:18 can. Otherwise, let's jump through this diagram. 0:22 We can see the first component here is the actor, which 0:26 will just be the user sending a request to our system and 0:30 ultimately create a reservation. 0:34 Now, each of these rectangles represent a 0:36 different microservice. 0:38 So of course, we have the reservations microservice 0:41 listening on 0:42 HTTP port 3000, and this is going to represent the 0:46 gateway to our system. It's going to be where the user is going 0:50 to send the request to actually create the reservation using 0:54 post/reservations route. Now you can see 0:57 here they need to first obtain a JWT, and 1:01 in order to get that JWT, we're gonna communicate with the auth 1:05 microservice on HTTP port 3001. 1:09 We're going to send a /login request with our user's 1:13 login credentials to the auth microservice. 1:16 Now, the auth microservice will also have a 1:19 route to create a user 1:20 which is going to persist users to our MongoDB database that you can 1:24 see is connected here. So the user will create an account, 1:28 and then they'll use the /login route to authenticate with 1:32 those credentials that will be stored in MongoDB. 1:36 And in exchange, they're gonna get back this JSON Web 1:39 Token, 1:40 which is a signed token and provides authentication 1:44 for future calls in the app. 1:47 So when we do make this post call to reservations, 1:51 the first thing it's gonna do is it's gonna take that JWT 1:54 and then send a 1:55 request to the auth microservice on TCP 1:59 port 3002. It's gonna use this message pattern
The rest of the transcript is for members.
Sign in 