I’ve found that this blog post by Tomislav Capan explains it very well: Why The Hell Would I Use Node.js? A Case-by-Case Introduction My interpretation of the gist of it, for Node 0.10, compared to Apache: The good parts Node.js avoids spinning up threads for each request, or does not need to handle pooling of … Read more
There won’t be much difference between EJB3 and Spring based on Performance. We chose Spring for the following reasons (not mentioned in the question): Spring drives the architecture in a direction that more readily supports unit testing. For example, inject a mock DAO object to unit test your business layer, or utilize Spring’s MockHttpRequest object … Read more
So I’ve been trying to figure out the real bottom-line when it comes to NoSQL vs RDBMS myself, and always end up with a response that doesn’t quite cut it. In my search there are really 2 primary differences between NoSQL and SQL, with only 1 being a true advantage. ACID vs BASE – NoSQL … Read more
What I will say in this answer is not specific to Kohana, and can probably apply to lots of PHP projects. Here are some points that come to my mind when talking about performance, scalability, PHP, … I’ve used many of those ideas while working on several projects — and they helped; so they could … Read more
For (heh) awesome fuzzy/partial string matching algorithms, check out Damn Cool Algorithms: http://blog.notdot.net/2007/4/Damn-Cool-Algorithms-Part-1-BK-Trees http://blog.notdot.net/2010/07/Damn-Cool-Algorithms-Levenshtein-Automata These don’t replace tries, but rather prevent brute-force lookups in tries – which is still a huge win. Next, you probably want a way to bound the size of the trie: keep a trie of recent/top N words used globally; for … Read more
Load balancing Most probably for the most simple sites you don’t need any scaling at all. Just one single box will get you covered. After that you should do load balancing like you are mentioning which is almost the same for every architecture(like you are saying you could start multiple node processes first. But when … Read more
A functional language doesn’t (in general) rely on mutating a variable. Because of this, we don’t have to protect the “shared state” of a variable, because the value is fixed. This in turn avoids the majority of the hoop jumping that traditional languages have to go through to implement an algorithm across processors or machines. … Read more
For very small numbers of sockets (varies depending on your hardware, of course, but we’re talking about something on the order of 10 or fewer), select can beat epoll in memory usage and runtime speed. Of course, for such small numbers of sockets, both mechanisms are so fast that you don’t really care about this … Read more
There’s nothing wrong with saving the whole history in the database, they are prepared for that kind of tasks. Actually you can find here in Stack Overflow a link to an example schema for a chat: example If you are still worried for the size, you could apply some optimizations to group messages, like adding … Read more