A queue would be a nice addition before the site goes live (it might be possible to employ a Redis list to do the job).
I'd love to see how far NodeJS could cope without the use of a queue though. I'm still something of a NodeJS novice but I'd guess that reading/processing every chunk inside a process.nextTick() callback would cause more disk IO problems than memory ones.
When I get the app running I might do some load-testing, the results would be very interesting.
I'd love to see how far NodeJS could cope without the use of a queue though. I'm still something of a NodeJS novice but I'd guess that reading/processing every chunk inside a process.nextTick() callback would cause more disk IO problems than memory ones.
When I get the app running I might do some load-testing, the results would be very interesting.