The issue with AWS is that administration and configuration of the server is on you, you will have to configure the server and IIS, I would suggest you to use appharbor instead, it's a PaaS hosting that uses Git for deployments and it's extremely pleasant to use, it's been in beta for almost a year and I find it very reliable, I have a production app on it without issues. Its infrastructure runs under AWS and you get to scale when you have to by adding more web servers on the control panel, and you dont have to configure the server yourself.
I would like to second the appharbor vote with the following two cents of advice...
I first tried to use MySql with appharbor using their MySql integrated service, but I found that it was difficult to use with multiple apps on the same database. I like to keep the admin app separate from the user app and I found that couldn't be done using appharbor best practices. I instead opted to use Amazon RDS directly from my appharbor app. You need to make sure they are in the same availability zones for performance, but this is working well for me.
I also keep an Amazon EC2 instance for worker processes that I run directly with the Task Scheduler on Windows b/c appharbor doesn't have support for worker processes yet.
This setup is working well for us...
My other gripe was some down time they had this past weekend... but this is bound to happen with any service, and they got it back up very quickly. They also now have integrated add-on StillAlive which I haven't used yet but am excited about.
发布评论
评论（2）
AWS 的问题是服务器的管理和配置由您负责，您必须配置服务器和 IIS，我建议您使用 appharbor 相反，它是一个 PaaS 托管，使用 Git 进行部署，使用起来非常愉快，它已经处于测试阶段近一年了，我发现它非常可靠，我在上面有一个生产应用程序，没有任何问题。它的基础设施在 AWS 下运行，必要时您可以通过在控制面板上添加更多 Web 服务器来进行扩展，而无需自己配置服务器。
The issue with AWS is that administration and configuration of the server is on you, you will have to configure the server and IIS, I would suggest you to use appharbor instead, it's a PaaS hosting that uses Git for deployments and it's extremely pleasant to use, it's been in beta for almost a year and I find it very reliable, I have a production app on it without issues. Its infrastructure runs under AWS and you get to scale when you have to by adding more web servers on the control panel, and you dont have to configure the server yourself.
我想通过以下两分钱的建议来支持appharbor投票...
我首先尝试使用他们的MySql集成服务将MySql与appharbor一起使用，但我发现很难在同一个数据库上与多个应用程序一起使用。我喜欢将管理应用程序与用户应用程序分开，但我发现使用 appharbor 最佳实践无法做到这一点。相反，我选择直接从我的 appharbor 应用程序使用 Amazon RDS。您需要确保它们位于相同的可用区以提高性能，但这对我来说效果很好。
我还为工作进程保留了一个 Amazon EC2 实例，我直接使用 Windows 上的任务计划程序运行该实例，b/c appharbor 尚不支持工作进程。
这个设置对我们来说效果很好...
我的另一个抱怨是他们在上周末遇到了一些停机时间...但这肯定会发生在任何服务中，并且他们很快就恢复了。他们现在还集成了附加组件 StillAlive，我还没有使用过它，但我对此感到很兴奋。
2012 年 5 月编辑：AH 现在为后台工作人员提供了选项，请查看此博客文章 http://blog.appharbor.com/2012/4/18/scheduled-tasks-using-quartz-and-appharbor-background-workers
I would like to second the appharbor vote with the following two cents of advice...
I first tried to use MySql with appharbor using their MySql integrated service, but I found that it was difficult to use with multiple apps on the same database. I like to keep the admin app separate from the user app and I found that couldn't be done using appharbor best practices. I instead opted to use Amazon RDS directly from my appharbor app. You need to make sure they are in the same availability zones for performance, but this is working well for me.
I also keep an Amazon EC2 instance for worker processes that I run directly with the Task Scheduler on Windows b/c appharbor doesn't have support for worker processes yet.
This setup is working well for us...
My other gripe was some down time they had this past weekend... but this is bound to happen with any service, and they got it back up very quickly. They also now have integrated add-on StillAlive which I haven't used yet but am excited about.
EDIT MAY 2012 : AH now has options for background workers, check this blog post http://blog.appharbor.com/2012/4/18/scheduled-tasks-using-quartz-and-appharbor-background-workers