适用于 WCF Windows 服务的 Amazon EC2
我有一个使用 .Net WCF、.net 4.0、SQL Server 2008 构建的同步服务，并托管在 Windows 服务中。
以下是我们完成的一些自定义实现；
自定义数据库连接池，在应用程序启动时填充，并且还有一个清理线程贯穿应用程序的生命周期。
自定义会话，因为应用程序不是要部署在 IIS 上，并且使用了 BasicHTTPBinding，因此实现了自定义会话。因此，Cleaup 线程也会运行来清除非活动会话。
[特定表]缓存，数据库中有一个特定的表，该表曾经被频繁命中，因此我们实现了自定义缓存以避免对数据库的过多命中，该缓存在应用程序启动时启动。
考虑到以上几点，请建议我以下；
此应用程序适合部署在 IIS 上吗？ （我认为部署在 IIS 上的应用程序仅在活动时保持活动状态，并在空闲时停止，因此缓存、池化将丢失并重新初始化）
Amazon EC2 是否适合于此？或者我应该注册 EC2 windows 实例？请向我介绍一下（我以前从未使用过 ec2，也没有太多相关信息）
是否支持故障转移集群？
有模拟帐户的选项吗？
Windows Azure 怎么样，我也应该考虑吗？
问候
I have a Sync Services built using .Net WCF, .net 4.0,SQL Server 2008 and hosted in a windows service.
Following are some custom implementation we have done;
Custom DB Connection Pooling, filled on the start of Application, and there is a cleanup thread as well which runs through out the life cycle of application.
Custom Sessions, as application was not targeted to be deployed on IIS and BasicHTTPBinding was used therefore custom session were implemented. Hence a Cleaup thread also runs to clear non-active sessions.
[Specific Table] Cache, There is a specific table in database which used to hit with a high frequency therefore we implemented a custom cache to avoid too many hits to database, this cache initiates at the start of Application.
With consideration of above points please Suggest me Following;
Is this application suitable to be deployed on IIS? (I thought application deployed on IIS, remains alive only in activity and stops when it gets idle, so caching, pooling will be lost and re-initialize)
Is Amazon EC2 is suitable for this; OR I should sign-up for EC2 windows Instance? please brief me on this(I have never used ec2 before nor having much information about it)
Is fail-over clustering is supported?
Is there any option for Demo Account?
What about Windows Azure should i consider that too?
Regards
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
如果空闲超时是您避免使用 IIS 的原因，那么我会说重新考虑，因为您可以禁用它：
如何禁用应用程序池空闲超时在 IIS7 中？
如果它正在热身，您会担心它已在 IIS8.0 中得到解决
http:// www.iis.net/learn/get-started/whats-new-in-iis-8/iis-80-application-initialization
甚至还有一个针对 IIS 7.5 的“预热”模块
http://www.iis.net/downloads/microsoft/application-initialization
您可以在 EC2 或 Azure 虚拟机上相当轻松地运行它。我不确定您所说的“Amazon EC2 适合此操作；或者我应该注册 EC2 windows 实例？”是什么意思，EC2 实例只是一个虚拟机，可以选择您想要的任何操作系统。
对于网络服务？您可以使用 Amazon Auto Scaling 和负载均衡器通过简单的 http 运行状况检查一次维护一定数量的服务器。
http://aws.amazon.com/autoscaling/
AWS 确实有一个免费套餐，它提供了足够的资源来测试和学习。
http://aws.amazon.com/free/
请注意，使用量是按小时计算的，例如您每月可以获得 750 个微实例小时，这意味着您可以运行 3 台服务器 250 小时。
是的。它不像 AWS 那样灵活，并且缺少一些功能，但 Azure 应该拥有您的用例所需的一切，并且可能会稍微便宜一些，并且更容易为 Windows VM 配置。
If the idle timeout is the reason you avoided IIS then I would say reconsider because you can disable it:
How to disable the application pool idle time-out in IIS7?
And if it's warm up you're worried about it's been addressed in IIS8.0
http://www.iis.net/learn/get-started/whats-new-in-iis-8/iis-80-application-initialization
And there's even a "Warm Up" module for IIS 7.5
http://www.iis.net/downloads/microsoft/application-initialization
You could run that fairly easily on either EC2 or Azure Virtual Machines. I'm not sure what you mean by "Amazon EC2 is suitable for this; OR I should sign-up for EC2 windows Instance?", An EC2 instance is just a virtual machine with whatever choice of Operating system you want.
For the web services? You use Amazon Auto Scaling and Load Balancers to maintain a certain number of servers at a time using a simple http healthcheck.
http://aws.amazon.com/autoscaling/
AWS does have a Free Tier which is just enough resources to test and learn.
http://aws.amazon.com/free/
Just note that usage is by hours, for example you get 750 Micro instance hours per month, which means you could run 3 servers for 250 hours.
Yes. It's not as flexible as AWS, and misses some features, but Azure should have everything you need for your use case, and may work out slightly cheaper, and is easier to configure for Windows VMs.