Ended up here after going through some other videos. Your tutorials are really good, you're doing a great job of explaining things well without all the fluff, and respecting peoples time. Thanks so much
Mario, you have really nice tutorials to understand different types of communications in gRPC! Very useful to code along with them. Moreover, in wearable.proto file, I see that CalculateBeatsPerMinuteRequest message is exactly the same as ConsumeBeatsPerMinuteRequest. Creating different pair of messages for each RCP method of a service, is it a convenion or a good practice? I see that this may become a scalability problem for huge systems. Why not reutilize messages in more than one rpc method?
Creating dedicated messages for requests and responses is a best practice; defining different messages allows you to add fields as needed, with that being said I understand the concern you're having so I recommend you to create messages that could represent a group of fields, for example if we were creating a message that returns "Address" values instead of using flat fields I'd create one message so it can be reused.
Very useful tutorial thank you. Can you make one more video on how we can create multiple client bidirectional streaming or can you suggest how i can do? Also i need to send message to specific client
Keep in mind a client connecting could work as a unique bidirectional channel, meaning if we have two clients client1 and client2, then we may be sending different messages depending on what they request; if you want to send specific messages then you need to define a "protocol", it does not have to be fancy it could be something like the client1 saying "i need messageABC" and client2 saying "i need messageXYZ".
I haven't really tried that, but I don't see why that couldn't be possible; you may need to implement your own "protocol" to determine when a file starts/ends but other than that in theory it seems possible.
Ended up here after going through some other videos. Your tutorials are really good, you're doing a great job of explaining things well without all the fluff, and respecting peoples time. Thanks so much
Thank you very much for this tutorial. Since my PC is slower, 30 fps is adequate for my needs.
Im following your series. Very useful! Great and noble job. Thx. Greetings from Cuba
Thanks for watching. Take care!
Mario, you have really nice tutorials to understand different types of communications in gRPC! Very useful to code along with them. Moreover, in wearable.proto file, I see that CalculateBeatsPerMinuteRequest message is exactly the same as ConsumeBeatsPerMinuteRequest. Creating different pair of messages for each RCP method of a service, is it a convenion or a good practice? I see that this may become a scalability problem for huge systems. Why not reutilize messages in more than one rpc method?
Creating dedicated messages for requests and responses is a best practice; defining different messages allows you to add fields as needed, with that being said I understand the concern you're having so I recommend you to create messages that could represent a group of fields, for example if we were creating a message that returns "Address" values instead of using flat fields I'd create one message so it can be reused.
Keep going Mario, fantastic content👏
Thanks Amir. Cheers!
Love the channel. Very useful and concise 🙏
Thanks Keith. Cheers!
Very useful tutorial thank you.
Can you make one more video on how we can create multiple client bidirectional streaming or can you suggest how i can do?
Also i need to send message to specific client
Keep in mind a client connecting could work as a unique bidirectional channel, meaning if we have two clients client1 and client2, then we may be sending different messages depending on what they request; if you want to send specific messages then you need to define a "protocol", it does not have to be fancy it could be something like the client1 saying "i need messageABC" and client2 saying "i need messageXYZ".
Te hizo falta GRPC que se está volviendo el más rápido para comunicación con poto buff y es muy seguro además de sencillo se usar
Can this bi-directional gRPC also send files?
Can you please reply to that, what modification we need to do for that?
I haven't really tried that, but I don't see why that couldn't be possible; you may need to implement your own "protocol" to determine when a file starts/ends but other than that in theory it seems possible.
Great job !!
Thanks Enrique! Cheers
Thanks 🙏
Does this work fine to be applied for real-time data transfer?
Yes, that's one use case.
@@MarioCarrion how about the server stream, can it work for real-time data update?
@@marcelezenagu9874 yes, either way: server, client or bidirectional, it depends on who is streaming data.
@@MarioCarrion how do you mean,"it depends on who is streaming data"
I'm looking to slide you dm on probably LINKEDIN