应用程序引擎停机
我注意到谷歌应用程序引擎似乎有相当长的停机时间，他们将数据存储区置于只读模式。这种停机时间通常发生在中午。这是仅在早期开发过程中发生的事情，还是我期望始终发生的事情？
我正在开发一个帮助小型企业处理运营的应用程序。它的一件事是接受预约，另一件事是路由电话。我想要一些关于如何处理数据存储处于只读状态的时间的建议，例如：
- 如果我们的客户正在与客户通电话并取消预约并且数据存储处于只读状态怎么办？要求客户稍后回来保存是不可接受的，尤其是在中午。
- 如果有来电并且应用程序由于数据库写入不可用而无法存储记录或正确路由呼叫怎么办？
通常如何处理此类问题？
I've noticed that google app engine seems to have a fair amount of downtime where they place the datastore into read-only mode. Frequently this downtime is in the middle of the day. Is this something that is happening only during early development, or is this something that I can expect to be always be occurring?
I'm developing an application that helps small businesses handle their operations. One thing that it does is take appointments, another is route phone calls. I'd like some suggestions on how to handle times when the datastore is in read-only such as:
- What if our client is on the phone with the customer and is taking down an appointment and the datastore is in read-only? It would not be acceptable to ask the client to come back later to save, especially if its in the middle of the day.
- What if there is an incoming call and the application can not store the record or properly route the call due to database writes being unavailable?
How are these types of issues normally handled?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
如果写入失败，您可以捕获数据存储异常并将任务排入队列以重试。如果写入继续失败，任务将自动重试，直到成功。
If a write fails, you can catch the datastore exception and enqueue a task to retry it. If the write continues to fail, the task will retry automatically until it succeeds.