Heroku 可靠吗？
我已经在 Heroku 上托管一个网站几个月了，很快就会投入生产。
自从我开始使用它们以来，至少发生了三次重大中断，其中一次是上个月发生的灾难性亚马逊中断，另一次是今天发生的长达数小时的中断。
我相信 Heroku 的愿景，并且认为他们是一家伟大的公司，但我面临着最终的问题：如果他们无法保持网站正常运行，那么我喜欢他们的一切都变得无关紧要。
Heroku 是在 Rails 上运行生产站点的可靠提供商吗？
我可能会考虑是否有其他提供商在可靠性方面比 Heroku 享有更好的声誉？
I have been hosting a site on Heroku for a few months that is very soon to go into production.
Since I began with them, there have been at least three significant outages, one of which was the disastrous Amazon outage last month and another of which is a multi-hour outage happening today.
I believe in Heroku's vision and I think they are a great company, but I am faced with the ultimate problem: if they can't keep sites up and running, everything I like about them doesn't really matter.
Is Heroku a reliable provider to run a production site on Rails?
Are there any other providers I might look into that have a better reputation for reliability than Heroku?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（7）
在我看来，几乎所有提供商都可能发生停机。您需要查看的是主机处理停机时间的情况如何，以及他们在向客户通报可能的解决方案的最新信息方面所做的努力。
在我看来，Heroku 是托管应用程序的好地方。在那里部署的优势和简便性弥补了我最近（且罕见）的停机时间。
In my opinion, downtime can happen with almost any provider. What you need to see is how well or badly the host handles the downtime and the effort they make in keeping the customer updated about possible resolution.
In my opinion Heroku is a great place to host your app. The advantages and ease of deploying there covers up for the recent (and rare) downtime FOR ME.
在过去的 7-8 个月里，我一直是带有 Amazon RDS 插件的 Heroku 用户，我的结论是，除了架构之外，Heroku 没有什么值得欣赏的地方。这就是我认为的原因：
http://don.blogs.smugmug.com/2011/04 /24/how-smugmug-survived-the-amazonpocalypse/
http://status.heroku.com/
我知道开发人员喜欢它，因为他们免费提供一个名为“dyno”的廉价网络进程。
I am user of Heroku with Amazon RDS plugin for the past 7-8 months and my conclusion is there is nothing to appreciate about Heroku except their architecture. Here is why I think:
http://don.blogs.smugmug.com/2011/04/24/how-smugmug-survived-the-amazonpocalypse/
http://status.heroku.com/
I know developers love it because they throw a cheap web process called 'dyno' for free.
到目前为止，Heroku 不提供多可用区冗余。如果您想要比 Heroku 更可靠的东西，您可以在多个可用区中创建自己的 EC2 实例。当然，这将需要更多的服务器维护、管理和部署时间。
So far Heroku does not offer multiple availability zone redundancy. If you want something more reliable than Heroku you can create your own EC2 instances in multiple availability zones. Of course this will require significantly more server upkeep, admin, and deployment time.
我觉得 Heroku 很可靠。我强烈推荐它来开始并验证你的想法。我相信当您开始项目时，您希望快速将其发布（向客户或公众）。
正如其他评论中提到的，在某些时候您可能需要切换到 EC2，因为您可能需要区域冗余，并且运行 EC2 实际上可能会变得更便宜，特别是如果您在公司中已经有 SA。
I have seem Heroku to be reliable. I highly recommended it for starting out and validating your idea. I believe when you start your project you want get it out quickly (to customer or to public).
As mentioned in other comments at some point you might need to switch over to EC2 as you might need zone redundancy and it might actually become cheaper to run of EC2 especially if you already have an SA in the company.
不，事实并非如此。作为一名客户，我经历过多次严重的停机。这些事情发生了，我明白了。但 Heroku 不可靠的原因是，当出现问题时，他们几乎不提供支持。在评估 Heroku 或任何提供商时，我会谨慎行事，并真正了解您所支付的费用。与我为 Heroku 付出的一样多，我期望更多。
举个例子，他们的一个数据库在周日早些时候就离线了。我立即意识到这一点，不是从 Heroku 那里，而是从我们的客户和新文物警报那里。我联系了 Heroku 支持人员，只是为了在开始排除故障时让事情顺利进行。 24 小时后，我几乎没有收到 Heroku 的回复。我无法按照他们的建议分叉、关注或拍摄数据库快照（因为他们遇到了问题），所以我基本上坐在我的手上等待。当我疯狂地试图以某种方式恢复时，希望有人能做出回应。
这是他们的错吗？不，一点也不。我应该/本可以做一些事情来减轻这种失败。但尽管我每个月为他们的服务支付了多少钱，我还是希望他们能够对我的关键问题做出类似的回应。
No. It is not. As a customer I've experienced multiple critical outages. These things happen and I get that. But what makes Heroku unreliable is their nearly non-existent support when things do go wrong. I would use caution when evaluating Heroku or any provider for that matter and really understand what you're paying for. Paying as much as I did for Heroku I expected more.
As an example one of their databases went offline early on a Sunday. I immediately was made aware, not from Heroku but from our customers and new relic alerts. I contacted Heroku support just to get the ball rolling as I began to troubleshoot. 24 hours later I had literally no responses from Heroku. I could not fork, follow, or take snapshot of the database as they suggest (because they were experiencing issues) so I basically sat on my hand and waited. Hoping that somebody would respond as I frantically attempt to recover somehow, someway.
Was this their fault. No. Not at all. I should/could have done something to mitigate this failure. But as much as I pay for their servies each month I expected something resembling a response to my critical issue.
我们的应用程序由 Heroku 托管，在过去 12 个月中多次出现故障。
有两次是由 Heroku 提供的第三方应用程序之一引起的：
我们使用 Zerigo（Heroku 推荐）作为我们的 DNS。这导致我们的网站两次宕机 - 其中一次需要 12 个小时才能恢复。对于 DNS 之类的东西来说，这绝对是疯狂的，因此我们已经转向更可靠的提供商。
Redistogo 应用程序宕机一次。
Heroku 确实带来了一些好处，但要小心您选择的应用程序。
Our our app is hosted by Heroku and went down mutliple times over the last 12 months.
Two times it was caused by one of the third-party apps that Heroku offers:
We used Zerigo (recommended by Heroku) for our DNS. This has caused our site to go down twice - one time it took over 12 hours te recover. This is absolutely crazy for something like DNS, so we have switched to a more reliable provider.
The Redistogo app went down once.
Heroku does bring some benefits, but be careful about the apps you select.
在我的组织中，我构建了简单的 SPA 生产力应用程序，并在从物理服务器迁移到云虚拟机后，去年一直使用 Heroku 来托管它们。
由于 Heroku 开发阻碍中断，我已经损失了多天的时间。通常，在运行应用程序时保持在线并工作，当 Heroku 出现故障时，您无法推送更新或重新启动应用程序。
我们也不要忘记定期维护的荒谬时间（通常是美国东部时间下午 2 点，周中……真的吗？）
在撰写本文时，Heroku 的日志系统现已运行（或多或少出现故障）超过 24 小时。
值得庆幸的是，我的应用程序不是关键任务。虽然我喜欢 Heroku 的易用性，但对于 AWS 中间人来说，不值得这么头疼。
也就是说，我将转向纯 AWS EC2 实例。
In my org i build simple SPA productivity apps, and have been using Heroku to host them for the last year after migrating away from a physical box server to cloud VMs.
I've had multiple days lost due to Heroku development hindering outages. Usually while running apps stay online, and work, when Heroku goes down you can't push updates or restart apps.
Lets also not forget the ridiculous times for scheduled maintenance (usually 2PM EST, midweek....REALLY?)
As of writing this, the Logging system for Heroku has now been acting up (more or less down) for over 24 hour.
Thankfully my apps aren't mission critical. While I like Heroku's ease of use, it's just not worth this much headache for what is nothing other than an AWS middle-man.
That said, I'm moving over to just pure AWS EC2 instances.