0:00 All right, so next up, I'm gonna show you how we can refactor 0:02 our, our 0:03 microservices. Instead of using TCP as 0:07 our transport layer for all of our microservices, we're instead gonna 0:11 use gRPC. 0:13 Now, if you're unfamiliar with gRPC, I'm gonna provide links to 0:17 both a introduction to gRPC, where you can quickly read up on 0:21 what gRPC is, as well as the language guide for it, 0:25 where you can learn more about Proto, which is the 0:28 language that runs gRPC. So I'll include links to both 0:32 of these later on in the course. However, just for a brief 0:36 overview, we can see a great description of what 0:39 gRPC is. 0:40 So we can see here that gRPC is gonna allow our client applications 0:44 to call methods on our server as if they were a 0:48 local object, which makes it really easy for us to build 0:51 distributed 0:52 applications. 0:54 So in gRPC, we define a service, the methods that the 0:57 service can be called, and all of the data that is involved 1:01 with those services, so the parameters, the return types. 1:05 All of this is gonna be defined in these proto files that we're 1:09 going to build. So we can see here that regardless of the client 1:13 we're using, whether it's a Ruby client, an Android client, or any 1:17 other client, the gRPC stub is gonna be exactly the same. 1:21 We're gonna talk to the server as if it was a local in-memory 1:25 process and get a response back. So this makes it super 1:29 easy to write our code once to define what our services look 1:33 like, and then any number of our clients can 1:35 reuse this, which 1:37 cuts down on duplication. 1:39 So I s- as I said before, gRPC runs on protocol 1:43 buffers, which we are going to work on building next in
The rest of the transcript is for members.
Sign in 