3 ms·

Could you please tell a few words about your application, if it is a million connections, it is a million * N database queries on the backend (for a typical web

Could you please tell a few words about your application, if it is a million connections, it is a million * N database queries on the backend (for a typical web app)? Would every request still stay in a queue, not on the front-end layer, but on database/storage/messaging/other middleware layer? I am just wondering what are the benefits of moving a bottleneck one layer up?

weaksauce 15y ago
Are you not using some sort of caching mechanism? a million queries to a db is probably going to kill it no matter what the front end.
- democracy 15y ago
  That's why I am wondering what types of applications require so many simultaneous connections. CDNs?
  - superted 15y ago
    The classical application that comes to mind is a chat app.
sh1mmer 15y ago
Not an application, just a benchmark. There was some keep-alive, and a small amount of state being passed from memory, but nothing heavy. At that level of contention you'll easily saturate a core making the application useless. My point is more that Node can support a very large amount of connections. Once you scale down to the tens or possibly low hundreds of thousands you can still do real work. This is mostly useful when you have a server that is looking after a lot of things that don't communicate very often. Sensors is one application for example. While totally passive sensors can poll a server with their data, being able to hold open many very cheap connections allows you ask sensors for their data when the server wants it rather than on an interval. This can cut down the amount of unnecessary data sent a lot.