Well, at every mid sized company I've been at, it's worked great. You can service a fuckton or clients off of one machine even with thread per connection. And

Well, at every mid sized company I've been at, it's worked great. You can service a fuckton or clients off of one machine even with thread per connection. And frankly, if well architected so much of the logic and business is well separated from the logistics, it's not the hardest thing (and by then there plenty of money to fund it) to rearchitect a thread per client model into something more effecient. It's hard to go wrong when you create a system initially and stick with the easy lower scale ways, like a single big MySQL (or oracle or postgres or even SQLite or whatever) database, thread per connection, etc. YAGNI, and if you do need it, get it when you do need it