你如何比较IIS&卡西尼作为生产服务器？ [英] How would you compare IIS & Cassini as production servers?

问题描述

我有一个正在IIS上运行的ASP.NET网站。现在我想把该网站移动到Cassini上运行。

Cassini在IIS上有什么优势？它的缺点是什么？

您将Cassini用作生产网络服务器的经验是什么？

解决方案

我会说你比较好，有一些被证明可以处理扩展的东西，比如mod_mono在apache上，如果你正在寻找替代服务器。

卡西尼不声称是多线程化或处理任何可能与iis有关的高级电子标签或其他标题控制问题，但通常也会在稍后版本的iis中设置为合理的默认值。

为了完整起见，您可以使用旧的rails-mongrels模型，在端口10100 - 10110上旋转10个cassini，然后使用ngenx或apache在这些线程上加载调度请求，并使用监视工具重做请求新的线程，当老人出去吃午饭，不断重新启动2左右的港口，因为你超载。

I have an ASP.NET website which is running currently on IIS. Now I want to move that site to run on Cassini.

What are the advantages of Cassini over IIS? What are its disadvantages?

What are your experiences using Cassini as a production web-server?

解决方案

I would say you are better off, going with something proven to handle scaling, like mod_mono on apache if you are looking for alternative servers.

The integrated pipeline, routing, compression and caching features of iis are hard to replicate. But the app pool and failure rapid response stuff is hard to do without knowledge of the OS and the network stack at a root level.

Cassini doesn't claim to be multi threaded or handle any of the advanced e-tags or other header control issues that can be issues with iis, but are also usually set at sensible defaults in later versions of iis.

For the sake of completeness, you could do the older rails-mongrels model, spin up say 10 cassini's on ports 10100 - 10110, then use ngenx or apache to load ballance requests on those threads, and using a monitoring tool to redo requests to new threads when old ones go out to lunch and constantly be restarting 2 or so ports, because you get overloaded.

这篇关于你如何比较IIS&卡西尼作为生产服务器？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！