Check out Express for a take on Node framework development. You can see some MVC there. The HTTP url parsing available in Node really makes writing a router easy for tossing requests to 'controllers' and requiring in models is easy.
Node can use a variety of databases from SQL (Postgres, etc) to No-SQL (CouchDB, Mongo, etc)
Here is an example of an already available "restart-node-on-changes" add-on
发布评论
评论（2）
查看 Express 了解 Node 框架开发。你可以在那里看到一些 MVC。 Node 中可用的 HTTP url 解析确实使编写路由器变得容易，以便将请求传递给“控制器”，并且模型中的需求也很容易。
Node 可以使用各种数据库，从 SQL（Postgres 等）到 No-SQL（CouchDB、Mongo 等）
这里是一个已经可用的“restart-node-on-changes”插件的示例
这里是 Node 的插件/模块列表
Check out Express for a take on Node framework development. You can see some MVC there. The HTTP url parsing available in Node really makes writing a router easy for tossing requests to 'controllers' and requiring in models is easy.
Node can use a variety of databases from SQL (Postgres, etc) to No-SQL (CouchDB, Mongo, etc)
Here is an example of an already available "restart-node-on-changes" add-on
Here is a list of plugins/modules for Node
典型的 Node.js MVC 应用程序会将模型数据存储在内存和某种保存的数据库（如 mongoose）中。
每次模型更改时，它都会通过您的 js 并保存到数据库中。它根本不需要重新启动。
如果您更改代码，您确实必须重新启动服务器。我认为有各种程序可以阻止这种情况的发生。
虽然它是 不推荐
这些也相关：EventedIO
A typical node.js MVC application would store the model data in memory and on some kind of saved database like mongoose.
Every time a model changes it goes through your js and saves to the database. It shouldn't need restarting at all.
If you change your code you do indeed have to restart the server. I presume there are various programs out there to stop this from happening.
Although it's not Recommended
These are also Relevant: EventedIO