blocks|key|3208577|text|我认为这篇博客文章很好地总结了这一点：http://debuggable.com/posts/understanding-node-js:4bd98440-45e4-4a9a-8ef7-0f7ecbdd56cb|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3208578|简而言之(pro+node.js)：|3208579|3208580|Speed|unordered-list-item|3208581|Javascript+(特别是如果你知道already)|3208582|Efficiency|3208583|的话|3208584|node.js真的很棒。试一试！:)|3208585|entityMap|0|LINK|mutability|MUTABLE|url|http://debuggable.com/posts/understanding-node-js:4bd98440-45e4-4a9a-8ef7-0f7ecbdd56cb^0|J|2E|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@$A|10|B|11|1|12]]|C|$]]|$1|D|3|E|5|6|7|13|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|14|8|@]|9|@]|C|$]]|$1|G|3|H|5|I|7|15|8|@]|9|@]|C|$]]|$1|J|3|K|5|I|7|16|8|@]|9|@]|C|$]]|$1|L|3|M|5|I|7|17|8|@]|9|@]|C|$]]|$1|N|3|O|5|6|7|18|8|@]|9|@]|C|$]]|$1|P|3|Q|5|6|7|19|8|@]|9|@]|C|$]]|$1|R|3|-4|5|6|7|1A|8|@]|9|@]|C|$]]]|S|$T|$5|U|V|W|C|$X|Y]]]]

I think this blog posts sums it up quite well:
<a href="http://debuggable.com/posts/understanding-node-js:4bd98440-45e4-4a9a-8ef7-0f7ecbdd56cb" rel="nofollow">http://debuggable.com/posts/understanding-node-js:4bd98440-45e4-4a9a-8ef7-0f7ecbdd56cb</a>

In short (pro node.js):

<ul>
<li>Speed</li>
<li>Javascript (especially if you know it already)</li>
<li>Efficiency</li>
</ul>

node.js is really great. Give it a try! :)

blocks|key|2995341|text|我之所以尝试使用node，是因为对于ajax请求，在服务器和客户端之间发送JSON数据非常容易。如果您使用像MongoDB这样的工具，它也可以将数据存储为JSON对象，那么您就不必担心转换或解析数据。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2995342|如果您的站点大量使用ajax，并且您以JSON对象(而不是XML或纯文本)的形式发送数据，那么node.js将为您节省不少精力。|2995343|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

My reason for trying out node is the fact that it is incredibly easy to send JSON data between the server and the client for ajax requests.
If you use something like MongoDB, which stores data as JSON object too, you never have to worry about translating or parsing your data.

If your site uses a lot of ajax, and you're sending your data as JSON objects (rather than XML or plain text) then node.js will save you a fair bit of effort.

blocks|key|286569|text|我能想到一个原因，但不是很深刻。基本上，如果你正在开发一个RIA，你的整个堆栈都可以是javascript。这可能会有一些价值。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|286570|但我会质疑我自己的答案，也就是说，即使它让客户端开发人员更容易访问服务器端代码，他们仍然需要了解他们的服务器堆栈是如何工作的。因此，我们还需要学习。|286571|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I can think of one reason, but its not very deep. Basically, If you are developing an RIA, your entire stack can be javascript. That might have some value. 

But Ill question my own answer, namely the thought is, even if it makes the server side code more accessible to client side developers, they still need to understand how their server stack works. So there is still some learning to.

blocks|key|3208688|text|准确地说，我认为您问题中的通用服务器端JavaScript引擎应该是V8，而根据它的创建者节点是为“编写网络程序脚本”而构建的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3208689|根据他的许多评论，我不相信他像我们中的许多人那样宽泛地看待它，但认识到它可以走向何方。我不能代表任何人发言--这只是我基于我所看到的作品和演示文稿的解释。|3208690|因此，它从较低的层次处理事情，使HTTP成为一等公民，而且非常酷，我认为这使它足够成为我们大多数人的“用例”。;)|3208691|它确实有一个学习曲线，而且由于它的快速发展，它并不是最稳定的构建平台。我相信时间会告诉我们它在哪里最有用。|3208692|目前，由于它的轻量级、异步特性以及一般的Web开发，人们将其用于“实时”应用程序，尽管IMO的甜蜜点仍然是它最初声明的目的。|3208693|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

To be accurate, I think the general server-side JavaScript engine in your question would be V8, while according to its creator Node was built for "scripting network programs."

Based on many of his comments I don't believe he views it as broadly as many of us do, but recognizes where it can go. [I can't speak for anyone else--that's just my interpretation based on the writings and presentations I've seen.]

So it approaches things from a somewhat lower level, makes HTTP a first-class citizen and just happens to be really cool, which I think makes it enough of a "use case" for most of us. ;)

It does have a learning curve and isn't the most stable platform to build on due to its rapid development. I believe time will tell where it's most useful.

For now people are using it for "real-time" apps due to its lightweight, asynchronous nature, as well as general Web development, though IMO its sweet spot remains with its originally stated purpose.

blocks|key|3208667|text|除了非阻塞I/O模型、可伸缩性和所有“主要原因”之外，我还喜欢node.js：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3208668|3208669|框架的轻量级本质。在github上构建大量有用的模块和库是很容易的，因为github扩展了learn.|unordered-list-item|3208670|Developer轻量级核心，而且capabilities.|3208671|It's非常容易和快速地构建服务器端和实时系统(例如，基于http或socket+)，而不需要了解复杂的库。|3208672|3208673|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|N|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|O|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|P|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|Q|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|L|$]]

What I like about node.js aside from non-blocking I/O model, scalability and all that "primary reasons" stuff:

<ul>
<li>Lightweight nature of it's framework. Basics are easy to learn.</li>
<li>Developer community building tons of useful modules and libraries on github which are expanding node.js lightweight core and it's capabilities.</li>
<li>It's really easy and fast to build server side and real-time systems (for example http or socket based) without the knowledge of complex libraries.</li>
</ul>

blocks|key|2995442|text|我喜欢使用NodeJS编写测试工具，因为您可以非常快速地编写存根/服务器/客户端。您可以轻松地驱动您的应用程序。我可以很容易地编写第三方后端服务器的脚本来对我的应用程序进行性能测试。我还用它来驱动我的应用程序。我可以使用setTimout执行复杂的客户端服务器场景，根据我想要的任何逻辑触发多个事件，并对它们进行大规模测试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2995443|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I like to use NodeJS to write testing harness because you can write a stub/server/client really quickly. And you can drive your application, with ease. I can easily script a third party back-end server to do performance testing on my application. I also use it to drive my application. I can perform complex client server scenarios using setTimout to cause multiple events to be trigger based on any logic I want and test them at scale.

The most common theme I read about why to use node.js is for high scalability due to it's evented, non-blocking I/O model. I'm trying to understand other non-scalability uses cases (and aside from being used as a general server-side javascript engine).

<ol>
<li>Does node.js have other use cases if scalability isn't a concern of mine?</li>
<li>If yes to #1, what are they?</li>
<li>Is node.js usage appropriate for any particular type of application architectures? E.g. similar to how some key/value (nosql - ugh I hate that term) databases are useful other than for scalability reasons.</li>
</ol>

What are some architectural reasons to use node.js aside from scalability?

数据存储

性能测试

数据库

服务器

MongoDB

JSON

我读到的关于为什么使用node.js的最常见的主题是，由于它的事件、非阻塞I/O模型，所以具有高可伸缩性。我正在尝试理解其他不可伸缩性的用例(除了被用作一般的服务器端javascript引擎之外)。如果可伸缩性不是我关心的问题，node.js是否还有其他用例？如果对#1有，它们是什么？是否适用于任何特定类型的应用程序架构的node.js使用？例如，类似于一些键/值(没有some -我讨厌这个术语)

问除了可伸缩性之外，使用node.js的一些架构原因是什么？
EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问除了可伸缩性之外，使用node.js的一些架构原因是什么？EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问除了可伸缩性之外，使用node.js的一些架构原因是什么？
EN