![]() It is lightweight and often (when implemented properly) has simple, easy to understand URLs. REST ( REpresentational State Transfer) is a design concept or architectural pattern, with a resource-oriented focus – software solutions are modelled as collections of resources that the user can access and interact with, using a consistent interface. So, without further ado, let’s kick things off with REST… REST: Well, yes – although they’re not exactly the same, they’re both still tools used for communication between web services that perform the same task / fulfill the same goal. ![]() gRPC is a framework, yet REST is an architecture / design concept, so is it really fair? REST is simple, straightforward and has widespread usage & support, while gRPC has better performance under load and has some nice features that cut out some of the annoying parts of REST (looking at you, headers).īefore we dive into comparing the 2, there’s one more question: Each has it’s pros and cons, but rather than “one true solution to rule them all”, both were pretty evenly matched. When we started designing our BuildVu Microservice Example, we did a fair bit of research into both REST and gRPC before deciding to go with REST. When building a new web-based service, one of the inevitable questions that comes up is “How am I going to talk to it?” Do you use REST? gRPC? …or maybe SOAP? In this post, myself and Ovi take a look at at both (and a quick glance at SOAP) to see if one is better than the other… In his spare time, he enjoys riding his motorcycle and playing guitar in his band.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |