12/19/2023 0 Comments Microservices grpc vs rest![]() ∙ HTTP/2 supports multiplexing of requests and responses. ![]() HTTP/2 helps gRPC to overcome some of the limitations with REST over HTTP 1.1 Moreover, gRPC is action-oriented, thereby helping developers to design flexible APIs. gRPC does all the heavy lifting work for inter-service communication leaving developers with only the task of defining a contract for remote procedure calls in a language-neutral format. GRPC is an open source framework developed by Google and currently managed under the aegis of Cloud Native Computing Foundation (CNCF). Network latency becomes significant especially for chatty interactions. ∙ A new TCP connection is established for every request/ response cycle in HTTP 1.1. This results in high bandwidth utilization. ∙ Data transfer in HTTP 1.1 is text-based and involves no compression of request headers. ![]() Therefore, JSON payload parsing is compute-intensive. ∙ JSON payloads are human-friendly, but they are bulky and not machine-friendly. This can be a limiting factor while dealing with API flexibility. However, this approach is suboptimal in the following scenarios: RESTful API carrying data in JSON is widely adopted as the most common communication pattern for connecting microservices together. Inter-service communication is one of the most critical design elements in a microservices-based solution that needs careful consideration. In the solution definition phase, it is quite easy to overlook some of the design complexities that arise when dealing with distributed systems as highlighted in Fallacies of Distributed Computing. The essence of microservices architecture is to build software as a set of autonomous business capabilities that collaborate non-invasively to realize the whole solution. However, microservices are complex to design. ![]() In this context, microservices have become the proverbial Holy Grail for solution architects to design and build modern software. As they say, change is the only constant. More than ever before, present day businesses want their IT systems to constantly evolve and be capable of responding positively to the changing goals and priorities. Guest post by Nikhil Mohan, Senior Technology Architect at Infosys ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |