8/6/2023 0 Comments Grpc vs rest api performance![]() ![]() A workaround could be a custom middleware layer, but this will introduce extra complexity in the architecture. Caching requests and responses are by default not supported in gRPC.Because maintaining a gRPC project could require new tools and knowledge which will add additional overhead to the maintainers. If gRPC is a new communication protocol for your tech stack, it could bring in some additional complexity.Therefore, a proxy layer grpc-web is required to perform conversion between HTTP/1.1 and HTTP/2 which also introduces extra complexity in the architecture. No modern browser provides the control needed over web requests to support a gRPC client.But this is likely to change soon as gRPC is getting adopted more and more. This could mean that gRPC could lack information about issues, proper documentation, best practices, workarounds, and success stories. If you compare gRPC 5.6k s/o questions to REST 90k s/o question or GraphQL 19.4k s/o questions.Lack of maturity, which could lead to a steep learning curve.When considering gRPC, make sure you are aware of the following limitations. It’s also wise to note that decisions could be made based on business constraints, e.g: What skills do we have with our current team? Or what is our budget for this project? gRPC limitations If that happens, try a small PoC with one or two communication protocols and check what fits best. Keep in mind that in a real life project, there are always requirements that do not fully match a given communication protocol. But this introduces extra complexity within the architecture by adding a proxy. In gRPC there is a workaround using grpc-web. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |