REST and Keep-Alive Web Service

I am setting up a service oriented web application. Part of the user interface (web application) consumes REST web services, which I also encode. Therefore, I have a hand on both the server side and the client side.

I'm just wondering if it makes sense to configure HTTP-keep-alive in such a context. If so, I am curious why.

early.

+4
source share
1 answer

Yes it is! From my testing on my server, I can get 300 calls per second to my REST web service without saving, more than 2000 with keepalive support.

You will need to do some analysis on usage patterns - often user use comes in during bursts, so it makes sense to keep the keepalive timeout pretty short, just to process one packet.

+7
source

Source: https://habr.com/ru/post/1445347/


All Articles