5 ms·
This article is spot on. We'd all like to have magical properties like speed and scale instantly conferred on our code merely by using the right tool. The fact
by andrewvc 14y ago
This article is spot on. We'd all like to have magical properties like speed and scale instantly conferred on our code merely by using the right tool. The fact of the matter is that both of those properties require consistent correct decisions at the application level to be achieved.
Scale, for that matter has been totally conflated with speed by many in the Node.js. A single-core reactor is not inherently scale-out. You can, of course, build a scale out app on node.js, but there's nothing about using node (or any other tool) that magically makes your app scaleable.
- bsimpson 14y agoRemember when App Engine came out? > Google: "Run your app on our servers, and you'll scale really well, just like Google." > Developers: "Sweet! Where do I sign up?" > Developers: "Wait - my app is actually really slow." > Google: "Duh! You have to write it exactly like we do to make it scale."
- FuzzyDunlop 14y agoI think question that could be asked is, how long can any one tool, used correctly, defer the need to scale? For some services, Node.js may give you more time and capacity. For others, Ruby or Python might. You might need a static website, and you can develop it and push out the 'compiled' HTML to your server. For all the scaley goodness Node.js or whatever may seem to offer, for that purpose it'd never compete with NginX running a static server with appropriate caching. Up until that point becomes visible on the horizon, you're just wasting time (and money) on a problem you don't or, if you're unlucky, might never have.
- wmf 14y agohow long can any one tool, used correctly, defer the need to scale? Probably longer if the tool automatically supports multiple cores.
- deleted 14y ago[deleted]