The first ibm video I’ve found useful. This guy knows what he’s talking about

This is a great informative video but a couple key points I think were missed/not as explicit: The binary serialization of gRPC messages is language neutral; meaning a component written in Java using some gRPC proto is interoperable with a component in C++, Go, etc,. HTTP 2.0 can utilize HTTP streaming capabilities which is sufficient for high bandwidth performant applications. gRPC has this implemented with the “stream” proto keyword that can be used for defined RPC call. This feature supports both uni-directional and bi-directional streaming. Backwards compatibility. One of the foundational reasons for gRPC’s inception was to avoid API breaking updates for new features. For example, imagine you have a bunch of client applications using a 1.0 iteration of your proto definition but your server upgrades to a 2.0 definition. In most other communication apis, all client applications would have to update to comply. However with gRPC this is not necessary, new fields are simply ignored by older client implementations. The key rule being you must keep legacy fields in proto files in the same place (the numbers in proto files dictate the position in the binary structure along with the size of the field). Another really nice feature of gRPC is the ability for multiple gRPC services to bind to the same server socket. This does require a single server process for this methodology but is useful for micro services that may need to provide multiple rpc calls. (No need to allocate a range of ports for services). Hope this info helps someone jump into gRPC! Here’s a link to my GitHub for anyone who’s interested: github.com/xTriixrx

this is the best lecture i have heard on gRPC.

Also, since proto schema is defined before generating stubs, the messages don't have to contain full keys. This actually saves a good amount of space.

Great breakdown… Love this guy’s flow

Clean and simple explanation , perfect intro. Thank you.

7:15mins of clean and good information. This helped me, thank you 🙏.

it's a really amazing powerful time saver. If you were around for COM & MIDL, gRPC & protocol buffers will blow your mind!

Wow! So Informative and well explained!! Thank you Mr Truong!

The main focus of the rpc framework is on service-to-service requests, typically owned by the same organization within the same data center. RESTful APIs have other benefits. It is suitable for experimentation and debugging and has a diverse ecosystem of tools.

Found it really helpful. Gonna explore more into it.

Worked with gRPC it also had performance issues when serialising collections. Maps, lists. We even had to convert to JSON string those collections and send them as string field og gRPC model. Maybe it is version specific but if you need to build fast services test serialisation performance for your particular data structure. From my experience it is not always linear depending on data volume.

This is an amazing tutorial. Short and crisp! Looking forward to more videos!!

Great content! This helped me understand

Really great video. Thanks!

Nice video, can I use gRPC in a EDA Architecture?

Very useful. Thank you.

Very good tutorial

is gRPC scalable? in terms of architecture it's a direct calls to the service instead of having event bus or queue to propagate message through can be messy. unless you're creating a gRPC gateway to propagate the messages to the microservices which adds things to build

Is it a re-upload? I watched the same video couple of days back. Not sure I had some crazy time travel 😀. Thank you for the video Brian.

but where does the Remote Procedure Call part come in?

How is no one talking about the fact that he‘s writing backwards?! What a unique skill to have, that is so useful here. Such a kool setup and style of presentation. Well done!

So protocol buffers are essentially language/platform agnostic schemas?

Great Information. I have a quick question. What is the technology or tool that you use to write on a screen like that?

Great video, although i would've loved a small section about gRPC coordination

great video

I don’t understand what is the difference between gRPC and google’s protobuf ?

In a nutshell, when we deal with a microservice architecture, we often need to somehow communicate from a microservice to another. This can be accomplished in quite a few ways: for a serverless architecture, for example, we could implement streams and query systems (AWS provides DynamoDB streams and SQS), for a typical (not serverless but actual servers) architecture, we can use a message queue like Kafka to keep services decoupled: i.e user signs up, user service creates the user and publishes an event and job done. Email service, which is subscribe to 'user-signup-event' will pick that up and send an email, for example. This is communication between microserverices in a decoupled and very good way. gRPC is a way of achieving this without a message queue by straight up call a function (procedure) from another service (thus remote) and do the job. Same result, different way. This is what the video should've said.

Feels like enterprise has fundamentally different needs (and thus addressment) of issues I’m not to worried about as a small business

Speaker says that we would have to import gzip library to perform gzip in our microservice while with grpc we dont have to. So how our data is being converted into binary when we use grpc? I assume that at the end of the day we also have some grpc dependency in our microservice to perform this conversion. If thats the case then i dont see the difference and dont know where is this convenience? :)

Did they reinvent the wsdl?

How did they flip the writing board? If he's writing onto a transparent surface and we should be seeing it flipped from the other side. Neat setup 👌

Does anybody know a good router for gRpc messages?

AWESOME

Does anybody know what he is using for the graphical representation? It looks cool!

My main question is how do you write backwards? Very impressive.

Energy of a school report.

So, compression is done by gRpc? How about encryption of messages?

It's really funny, because in a well designed microservice system, they are not making a lot of calls to each other, making gRPC less useful the better designed a system is.

tks

Well… I’m thinking about the truly “convenience” when you have to import the same library in different codes and creates new layers of configuration to deal with the descriptors of the services… looks like an kind of SOAP protocol.. and binary the communication to improve performance… it’s ok.. but.. that’s it ?? Nothing more ?

Honest question: Isn't it considered best practice for microservices to not call each other?

Good summary

Fast way for creating distributed monolith

Is it good for services in micro services to directly communicate?

How you do you transmit the json string without serialization? anything that's sent over the network is serialized right? so json is also transmitted as binary?

Unfortunately, this was way over my head. Maybe this was more for another audience, but I didn't quite get what a gRPC is from this. Let me look at it again...

Heater 🔥🔥🔥🔥

Can I ask what sofeware are you using to record this kind of vedio?

interestingly Kryo serialisation is still way faster and produces smaller data, however is not a standard and not used for interoperability :/

This guy is pretty smart! I bet he spends a lot of time studying at a top university.

SOAP ? XD

You don't have to implement gzip compression of JSON data, because http server will do it for you.

The winner: JSON-RPC

hi, is grpc only for MS or Server client like spriing boot and flutter great? how this think know url adresses like Rest?

so is he left handed or right handed???????

Does anybody wonder how did this guy write with his left hand and in backwards?

Go bestie! Go bestie !

How is he writing in mirror image so effortlessly?!

Mmmm so it remainds me of RMI

Does anyone knows, why my GMS soft soft is diffrent ?

you should not have to do anything special to gzip requests and responses, plaintext or JSON. Just make sure your server is configured to do it. It will add the Content-Encoding: gzip header and the rest should work out on it's own. Any http client out there should already know how to handle that, it is spart of the http specs.

Beware size limit 4 MB.

so you re-invented soap?

You guys should consider slides tbh.

eXcellent

How is this guy writing backwards so effectively?

Do you guys really write backwards? Or it's just camera trickery? 😂

Not Understanding

REST is king. Anything else is just trying to get back to the dark ages of Corba and Webservices. I am quite sure there is some heavy payload situations that need gRPC but we should stick with REST as much as we could, and stop going back to the nightmares of yesteryears in the name of "we can do that with better performance."

“I’m not talking about communication between the front-end and back-end” [draws arrow anyway]

Cute guy

Unclear

bro why are you writing backwards. very distracting :D

very great video