Learn how to integrate asynchronous messaging into your application & achieve scale with Apache Pulsar. Includes deployment on Kubernetes.
Length 1:23:30
Captions English (Generated), Spanish (Auto-translated), French (Auto-translated), Korean (Auto-translated), Portuguese (Auto-translated), Vietnamese (Auto-translated) #apache pulsar #nestjs #kubernetes #docker #message queue #microservices #distributed systems #backend development #streaming platform #cloud native
0:00 Hey there. Today we're gonna take a look at Apache 0:02 Pulsar. 0:03 So Apache Pulsar is a cloud native distributed messaging and 0:07 streaming platform built from the ground up to be extremely 0:11 scalable and elastic. So it's similar to Kafka in the way 0:15 that it's 0:15 gonna allow us to distribute messages and do work 0:19 asynchronously with inside of Node.js, which is a very common 0:23 pattern when we're trying to distribute work horizontally over 0:27 perhaps many different instances of our application, which allows 0:30 us to scale our app up. So Pulsar is gonna allow us to do this. 0:34 In this video, we're gonna see how that's possible. 0:37 Let's jump right in and see how we can incorporate Apache 0:40 Pulsar into a 0:41 NestJS backend. I'll see you there. 0:44 To bootstrap our application, we're gonna utilize the NestJS 0:48 CLI to actually create our NestJS application for us. 0:52 So if you don't have this, you can install it with NPM. 0:56 Go ahead and install it globally, the 0:58 @nestjs/cli@latest. Go ahead and 1:02 install this. 1:04 And then we can use nest new to generate a new application, and I'll 1:08 call this nestjs-pulsar. I'm also gonna use 1:12 pnpm as my package manager, and let's go ahead and let our 1:15 dependencies get installed. 1:18 So now we can CD into our application, and you can see 1:22 here that we can immediately start our server. 1:24 Let's go ahead and start it in development mode by running 1:28 pnpm start:dev. 1:32 So our app has started up successfully and is ready to accept 1:36 HTTP requests. Let's go ahead and open it up in VS Code. 1:40 So we have our default NestJS application initialized here, 1:44 and of course, we can see in our source directory we're 1:47 starting our application 1:48 in our bootstrap function, where we're accepting incoming traffic on 1:51 port 1:52 3000. We have our root app module that's going
The rest of the transcript is for members.
Sign in 