3 ms·
On the contrary I like it. They have finite resources and it answers immediately with the correct response.
by thu 14y ago
On the contrary I like it. They have finite resources and it answers immediately with the correct response.
- St-Clock 14y agoThis. With typical web applications, your request would wait until something times out and cascades back to the client (webserver, app server, db, etc.). This can mean waiting for 30 seconds or more depending on your configuration. It's not an easy problem to solve elegantly too.
- pixelbath 14y agoIt actually is quite easy if you set a finite limit on connections and show an appropriate message to those connections you're actively refusing. If you're allowing as many connections as your server/network/database can allow, it might take a bit longer to determine a failure status.