|
|
DDD888 发表于 26-6-2014 18:41
这是否意味着写node.js门槛比写C# asp.net mvc更低，导致做的人更多，更加不容易将工资升上去？
我没写过.net的程序，不敢妄自评论。不过我相信一些技术含量低的server端开发，会有更多人能做。
但是目前node.js也不是万能的，有些应用场合还不适合（如部分传统SQL数据库的操作，需要大量CPU运算的后台API），这篇文章列举了一些例子（不完全对，因为Node.JS也在快速演进中，今天的不适合明天可能就适合了）：
Where Node.js Shouldn’t Be Used
http://www.toptal.com/nodejs/why-the-hell-would-i-use-node-js
1. SERVER-SIDE WEB APPLICATION W/ A RELATIONAL DB BEHIND
Comparing Node.js with Express.js against Ruby on Rails, for example, there is a clean decision in favour of the latter when it comes to relational data access.
Relational DB tools for Node.js are still in their early stages; they’re rather immature and not as pleasant to work with. On the other hand, Rails automagically provides data access setup right out of the box together with DB schema migrations support tools and other Gems (pun intended). Rails and its peer frameworks have mature and proven Active Record or Data Mapper data access layer implementations, which you’ll sorely miss if you try to replicate them in pure JavaScript.
Still, if you’re really inclined to remain JS all-the-way (and ready to pull out some of your hair), keep an eye on Sequelize and Node ORM2—both are still immature, but they may eventually catch up.
2. HEAVY SERVER-SIDE COMPUTATION/PROCESSING
When it comes to heavy computation, Node.js is not the best platform around. No, you definitely don’t want to build a Fibonacci computation server in Node.js. In general, any CPU intensive operation annuls all the throughput benefits Node offers with its event-driven, non-blocking I/O model because any incoming requests will be blocked while the thread is occupied with your number-crunching.
As stated previously, Node.js is single-threaded and uses only a single CPU core. When it comes to adding concurrency on a multi-core server, there is some work being done by the Node core team in the form of a cluster module [ref: http://nodejs.org/api/cluster.html]. You can also run several Node.js server instances pretty easily behind a reverse proxy via nginx.
With clustering, you should still offload all heavy computation to background processes written in a more appropriate environment for that, and having them communicate via a message queue server like RabbitMQ.
Even though your background processing might be run on the same server initially, such an approach has the potential for very high scalability. Those background processing services could be easily distributed out to separate worker servers without the need to configure the loads of front-facing web servers.
Of course, you’d use the same approach on other platforms too, but with Node.js you get that high reqs/sec throughput we’ve talked about, as each request is a small task handled very quickly and efficiently.
这个问答也不错：
http://stackoverflow.com/questio ... when-to-use-node-js |
|
发表于 25-6-2014 05:43:30
如何谈高工资？如何去得到这份工作
收藏
赞
踩
楼主
发表于 25-6-2014 10:51:30
发表于 25-6-2014 19:48:26
