gRPC vs REST - KEY differences and performance TEST

Рет қаралды 34,617

Jelvix | TECH IN 5 MINUTES

Күн бұрын

Пікірлер: 36

@Jelvix Жыл бұрын

What do you prefer to use more - gRPC or REST? Tell us your opinion on these two... 🤯

@usernamename2978 2 ай бұрын

If I had a useful opinion, why would I be here to watch this?

@JaneMoir Жыл бұрын

I've been curious about gRPC and REST differences for a while now. This vid was super informative and helped me so much... Thanks! ☺

@jiminnovator1556 Жыл бұрын

Absolutely loved this comparison! Thanks for shedding light on this topic!

@davidhunter3605 9 ай бұрын

Wow totally meaningless performance tests. What did you measure exactly? How did you measure it? Basically you might as well have produced random numbers as you don't say what you tested.

@Jelvix 5 ай бұрын

Hi! Thank you for your feedback! We are creating the short videos so we can’t explain everything. But we will discuss your comment for our future videos! Thank you!

@monicasmith6007 Жыл бұрын

This was eye-opening! Which one, gRPC or REST, would you suggest for IoT applications and why?

@jefersonnl 4 ай бұрын

I don't know about you, but I often choose for an IoT project the simplest and cheapest hardware able to do the job, that is a good philosophy. Keep it simple, no overkills. Sometimes that can be an ATMega board hooked to an ESP-01, a STM32 MCU with built in board connectivity, or even an ESP32 board. I will always use the cheapest and simplest board I can get await with. More than that is overkill, like a Raspberry Pi for instance. Other coding language working on a higher level than C is also overkill, unless libraries that you *MUST* make use of demand so. That being said, REST is the king here, due to its minimalistic and simplistic approaches to communication. It also supports several forms of authentication, and you can fiddle around with the best one for your scenario, that is (due to the nature of IoT constrictions and restrictions)usually the simplest and less resource intensive one that wouldn't of course compromise security. Its also difficult to imagine how things like gRPC and GraphQL would have a smaller implementation footprint than REST in such restricted devices.

@keplerk 9 ай бұрын

A question would be, how costly it's to keep and maintain grpc compared to a simple rest api.

@Jelvix 9 ай бұрын

Thank you for this question! We'll take it into account in our upcoming videos

@jefersonnl 4 ай бұрын

Very good one. Another good question: GRPC vs AMQP RPC, costs of implementation(specially if you already have AMQP in use for other stuff in your infrastructure), and performance.

@GauriSpirit Жыл бұрын

Nice explanation

@amirbaha2ri 9 ай бұрын

Consider I just need a simple CRUD and a few actions for my own business and there is no importance how hard is implementing each one of REST or gRPC. Can I choose gRPC just for getting experienced in it, and I can hope will not face any problem that wouldn't happen with REST?

@Jelvix 4 ай бұрын

If you're looking to get hands-on experience with gRPC, it's definitely a great choice for learning, even for a simple CRUD application! However, keep in mind that gRPC has a steeper learning curve and might require more setup, especially around things like HTTP/2, protocol buffers, and client libraries. That said, for a small-scale project, you shouldn’t run into any significant problems that wouldn’t happen with REST - just be aware that REST might be more straightforward for basic CRUD operations due to its wide adoption and simplicity. If you're comfortable with the extra setup, go for gRPC and enjoy the learning

@fcnealvillangca7943 11 ай бұрын

as new to industry I take Rest API because it's stable. we tried GraphQL but it didn't fix the problem infact it only introduce extra work to the backend. I will just adjust to graphql , grpc, trpc etc etc incase the Job requires to. But what can you suggest

@RayParker 9 ай бұрын

I found GQL a God send in the Rails world - if you know how to use it. I’ve reduced server loads up to 70% v REST + Rails classic MVC.

@RayParker 9 ай бұрын

Oh, and back end work quickly declines as the API matures.

@KaiGan-mk1mh 5 ай бұрын

REST can use protobuf to comminicate right?

@Jelvix 5 ай бұрын

Yes, REST can use Protocol Buffers (protobuf) for communication, although it's not very common

@jeremypatrick7853 9 ай бұрын

Perhaps a combination of the two? REST for minimal data that needs to be transported, and any large sets of data using gRPC, isn't that supposed to be the beauty of microservices?

@Jelvix 4 ай бұрын

Great point! A combination of REST and gRPC can indeed be a powerful approach. REST works well for simpler, lightweight data transfers and broader compatibility, while gRPC shines with performance when dealing with larger datasets or requiring high efficiency in communication between microservices. Leveraging both plays to their strengths and aligns perfectly with the flexibility and scalability that microservices architecture offers!

@ungrim97 Ай бұрын

This feels like the person who wrote it didn't understand REST. REST API's typically use JSON because its easy for humans to read, and has a wide parsing support. *BUT* it doesn't have to. the payload can be serialsed in any way you like, including using protobuffs. REST is mearly the idea that the client and the server should use the HTTP meta data as a means to define behavior rather than duplicating that data in the request/response. RPC is wasteful in that it replicates lots of the HTTP standard (such as status codes, and action verbs) and each api is unique in teh supported set of methods. REST attempts to unify access patterns to a series of well understood CRUD actions. RCP allows for more flexibility for things outside this remit

@Jelvix 28 күн бұрын

Hi! Thank you for your detailed feedback! Our goal was to simplify the core concepts for a broader audience, but we appreciate your clarification and will aim for even more precision in our future content!

@usernamename2978 2 ай бұрын

"...features such as ... ... ... and more". This is word soup. How can you end a list of examples with "and more"? You don't appear to understand the notion of an example: you may as well say "...features such as features".

@Jelvix 2 ай бұрын

Hi! Thank you for your advice!

@EveEudora-g6l 4 ай бұрын

Skiles Corners

@Jelvix 4 ай бұрын

Excuse me?

@BoyangLyu 4 ай бұрын

The gRPC is only a little bit faster than REST

@Jelvix 4 ай бұрын

Hi! Thank you for sharing your opinion!

@ElsieDixon-o2e 5 ай бұрын

Jones Robert Harris Frank Allen Richard

@Jelvix 5 ай бұрын

🤔🤔🤔

@GameDevChad 27 күн бұрын

More than 99% of programmers don't know how to establish a TCP connection and need a library to send data. More than 90% are unable to use anything that is not HTTP. Pathetic.

@Jelvix 20 күн бұрын

Thank you for sharing your perspective! It’s true that many developers rely on libraries and frameworks to handle complex tasks like establishing TCP connections or working outside of HTTP, and that's often because these tools are designed to simplify development and improve productivity. While not every developer needs to work at the protocol level, understanding the fundamentals of networking is definitely valuable. We appreciate your comment and will consider exploring more low-level topics in future content.