I am just curious if I am missing in some such http2 which is more efficient in service-to-service communication For example, in a microswave architecture
Is it correlated with an end-user (browser)?
If you are issuing several concurrent requests between the microservice, then its benefit. You do not need to manage the TCP connection pool on the client, and restrict the number of TCP connections that come in the service side.
Some services may benefit from server push, although it really depends on the service. Header compression can be useful if you have high traffic volume in service with repeated meta-data. More information can be found.
In short, yes, it is designed with end users in mind, but it is also worth due to the reciprocal micro services as well as connection multiplexing.
No comments:
Post a Comment