The application is planned to be built using ASP.NET, .NET Remoting & MS SQL Server. High availability is required at presentation layer, application layer and database.
该应用程序计划使用ASP.NET,.NET Remoting和MS SQL Server构建。表示层,应用程序层和数据库需要高可用性。
Does IIS 7.0 provide any advantages over IIS 6.0 in regard to the High availability aspect?
IIS 7.0是否在高可用性方面提供了优于IIS 6.0的任何优势?
3 个解决方案
#2
2
Among the many aspects you want to consider, make sure that you have numbers.
在您想要考虑的许多方面中,请确保您有数字。
By numbers, I mean how many request per second do you want to deliver? How many users per day are you planning? Are they all going to come in 1 hour or through out the day? Are they simply buying stuff on a e-Commerce website or is it a social network website with lots of pictures and videos?
按数字,我的意思是你想要提供每秒多少请求?您计划每天有多少用户?它们都会在1小时内或在一天之内到来吗?他们只是在电子商务网站上购买东西,还是一个拥有大量图片和视频的社交网站?
All those questions matters in how you will architecture your website. If you go with a simple e-Commerce website that should not crash, make sure to have 2 servers with load balancing with some health monitoring on the IIS process. For the database, 1 machine will do the trick especially if you have some RAID hard drives.
所有这些问题都与您如何构建网站有关。如果您使用一个不应该崩溃的简单电子商务网站,请确保在IIS进程中有2台服务器具有负载平衡和一些运行状况监视。对于数据库,1台机器将完成这项工作,特别是如果您有一些RAID硬盘驱动器。
However, if you go toward a social network site... things get freaky fast. If users upload pictures, you will need lots of space and much more if they upload videos. You might want to use Cloud Service to host those pictures without too much fees. For videos, you might want to use embeded link like Youtube or Google video.
但是,如果你走向一个社交网站......事情会变得很快。如果用户上传图片,如果他们上传视频,您将需要大量空间和更多空间。您可能希望使用Cloud Service托管这些图片而不需要太多费用。对于视频,您可能希望使用嵌入式链接,例如Youtube或Google视频。
As for IIS 7.0 versus IIS 6.0, I don't think there will be any significant changes. Both are really reliable.
至于IIS 7.0与IIS 6.0,我认为不会有任何重大变化。两者都非常可靠。
#3
0
Make sure your design scales in a horizontal manner.
确保您的设计以水平方式缩放。
That is, have your system hiding behind a load balance layer with the servers that are actually providing the service behind the load balance layer.
也就是说,让您的系统隐藏在负载平衡层后面,其中服务器实际上是在负载平衡层后面提供服务。
When you need to increase capacity, you build a new server or servers and plug it in alongside the existing servers. Then you configure the load balance layer to also consider the new server(s) when passing out the work.
当您需要增加容量时,您需要构建一个或多个新服务器并将其与现有服务器一起插入。然后配置负载平衡层以在传递工作时考虑新服务器。
#1
#2
2
Among the many aspects you want to consider, make sure that you have numbers.
在您想要考虑的许多方面中,请确保您有数字。
By numbers, I mean how many request per second do you want to deliver? How many users per day are you planning? Are they all going to come in 1 hour or through out the day? Are they simply buying stuff on a e-Commerce website or is it a social network website with lots of pictures and videos?
按数字,我的意思是你想要提供每秒多少请求?您计划每天有多少用户?它们都会在1小时内或在一天之内到来吗?他们只是在电子商务网站上购买东西,还是一个拥有大量图片和视频的社交网站?
All those questions matters in how you will architecture your website. If you go with a simple e-Commerce website that should not crash, make sure to have 2 servers with load balancing with some health monitoring on the IIS process. For the database, 1 machine will do the trick especially if you have some RAID hard drives.
所有这些问题都与您如何构建网站有关。如果您使用一个不应该崩溃的简单电子商务网站,请确保在IIS进程中有2台服务器具有负载平衡和一些运行状况监视。对于数据库,1台机器将完成这项工作,特别是如果您有一些RAID硬盘驱动器。
However, if you go toward a social network site... things get freaky fast. If users upload pictures, you will need lots of space and much more if they upload videos. You might want to use Cloud Service to host those pictures without too much fees. For videos, you might want to use embeded link like Youtube or Google video.
但是,如果你走向一个社交网站......事情会变得很快。如果用户上传图片,如果他们上传视频,您将需要大量空间和更多空间。您可能希望使用Cloud Service托管这些图片而不需要太多费用。对于视频,您可能希望使用嵌入式链接,例如Youtube或Google视频。
As for IIS 7.0 versus IIS 6.0, I don't think there will be any significant changes. Both are really reliable.
至于IIS 7.0与IIS 6.0,我认为不会有任何重大变化。两者都非常可靠。
#3
0
Make sure your design scales in a horizontal manner.
确保您的设计以水平方式缩放。
That is, have your system hiding behind a load balance layer with the servers that are actually providing the service behind the load balance layer.
也就是说,让您的系统隐藏在负载平衡层后面,其中服务器实际上是在负载平衡层后面提供服务。
When you need to increase capacity, you build a new server or servers and plug it in alongside the existing servers. Then you configure the load balance layer to also consider the new server(s) when passing out the work.
当您需要增加容量时,您需要构建一个或多个新服务器并将其与现有服务器一起插入。然后配置负载平衡层以在传递工作时考虑新服务器。