如何创建可靠的移动服务

发布于 2024-10-17 08:04:41 字数 540 浏览 8 评论 0原文

我开发了一个广泛使用网络服务的移动应用程序。它连接到我的共享托管服务器以获取实时信息。因此,确保服务器正常运行非常重要。否则我就会失去客户。

一些背景。我更换了不少于 3 个托管提供商,因为他们在正常运行时间方面不太可靠。我当前的托管比前三个要好得多,我现在使用它已经一年多了,他们有 99.9% 的正常运行时间保证等等,但今天我有大约 3 个小时的停机时间。这就是我创建这篇文章的原因。

并非我们所有的小型开发人员都能负担得起昂贵的专用托管,或者在家里拥有自己的服务器(这并不能保证它永远不会宕机)。就我而言,以非常合理的价格每月 10-15 美元购买共享主机就可以了。除了那几个小时之外,它可能会下降。

我必须处理这个问题的一个想法如下:与另一个提供商共享第二个(不同的)托管,并让应用程序在我的主要主机关闭时默认使用第二个托管。两者同时下降的可能性很小。我每月只需为此额外支付几美元,而不是像专用托管那样每月多付 10 倍。

我确信我不是第一个遇到这种情况的人。有没有人找到解决这个问题的好方法,而不需要雄厚的财力?毕竟,我们讨论的只是主服务器上的短时间停机。

预先感谢您的建议。

I have developed a mobile application which is using extensively web services. It connects to my shared hosting server to get real-time information. Therefore, making sure the server is up is extremely important. Otherwise I am going to lose customers.

Some background. I changed no less than 3 hosting providers because they were not very reliable in terms of uptime. My currrent hosting is way better than those previous three, have I used it now for over a year, they have 99.9% uptime guarantee and all, but today I had about 3 hours of downtime. Which is why I am creating this post.

Not all of us small developers can afford expensive dedicated hosting, or have our own servers at home (which is not a guarantee it never will be down). In my case, having shared hosting for a very reasonable $10-15/month is OK. Except for those few hours it might be down.

One idea I have to deal with this is the following: have a second (different) shared hosting with another provider, and make the app to default to using this second hosting when my primary host is down. It's very unlikely that both will be down at the same time. I am going to pay only a few dollars extra per month for this, not 10 times more per month as I would for a dedicated hosting.

I am sure I am not the first person in this situation. Have anyone found a good way to deal with this problem, not requiring deep pockets? We are after all talking only about short periods of downtime on the primary server.

Thanks in advance for your suggestions.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

弃爱 2024-10-24 08:04:41

如果您依赖第三方主机并且不想为更高的可靠性付费,那么第二台服务器是最佳选择。根据您的应用程序和预算,您还需要考虑:

  • 数据库访问和同步
  • 位于不同物理位置的主机
  • 多个域名和/或负载平衡

如果您选择使用多个主机并切换到不同的(备份)主机,如果其中一个(首先)失败,那么您应该致力于始终使两者(全部)始终处于使用状态。这样您就不会在尝试/必须切换到“备份”服务器时陷入困境。通过始终使用两者(全部),您可以确保它们(全部)始终保持最新且正常工作。

如果您的服务非常重要,以至于用户无法接受几个小时的停机时间,那么应该很容易让用户为这种可靠性付费。这可以为能够提供更高水平正常运行时间或第二个站点的提供商提供托管资金。这也将有助于为建立这一切提供时间和精力。 ;)

If you are relying on a third party host and don't want to pay for greater reliability then a second server is the way to go. Depending on your application and budget you will also need to consider:

  • Database access and synchronization
  • Hosts in different physical locations
  • Multiple domain names and/or load balancing

If you opt to use multiple hosts and switch to a different (backup) host if one (the first) fails then you should aim to always have both (all) always in use. This way you won't get caught out trying/having to switch over to a "backup" server. By always using both (all) you can be sure that they are both (all) always up to date and working.

If your service is so critical that a couple of hours down time would be unacceptable to your users, then it should be easy to get the users to pay for that kind of reliability. This could fund hosting with a provider who can provide a greater level of up time or a second site. This will also help fund the time and effort to set all this up. ;)

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文