Thursday 4th November, 2010
2:05pm to 3:05pm
There doesn't need to be a trade off between application performance and ease of programming. Node.js abstracts the problem of concurrency well; programmers with little experience tend to create servers that scale into the thousands of connections. For example, at Node Knockout, a Node.js programming contest, in 48 hours contestants developed sites that were handling thousands of requests per second, pushing 80 megabits/sec - using less than 256mb memory, less than 1% CPU, in a single process. By addressing the hard architectural problems head on, many development cycles of rethinking may be saved by choosing a completely asynchronous system.
Sign in to add slides, notes or videos to this session