Asynchronous processing in gae.

在GAE中异步处理。

GAE provides a management interface.

GAE提供了一个管理界面。

In GAE, it also requires queuing.

在 GAE 中，它也需要排队。

A task in a GAE queue is just a servlet.

gae队列上的任务刚好是一个servlet。

Let's see how to deal with this in the GAE.

让我们看看如何在GAE中处理此问题。

Now your application is deployed to the GAE.

现在已经把应用程序部署到GAE中。

The next step is to deploy the application to GAE.

下一步就是将应用程序部署到 GAE。

Figure 4 shows the application running on GAE.

图4展示了运行在GAE之上的应用程序。

Overall, GAE provides a well-designed and scalable PaaS.

总体而言，GAE提供了精心设计并可伸缩的PaaS。

The GAE is a platform for creating Web applications.

GAE是创建Web应用程序的平台。

As you might know, GAE is a dynamic clustered environment.

您可能已经知道，GAE是一个动态的集群环境。

In some cases, GAE is simply ruled out for this very reason.

有些情况下，GAE仅仅只是排除了这个原因。

The GAE datastore leverages an index for any query issued.

GAE数据存储对发出的任何查询使用索引。

GAE provides excellent integration with other Google services.

GAE提供与其他Google服务的出色集成。

That's fine, except that GAE allows only 100 indexes per table.

这很好，除了GAE只允许每个表100个索引以外。

That makes GAE an unreliable platform for mashup-type applications.

这使 GAE 成为不可靠混合类型应用程序平台。

To make the GAE scalable, it cannot be tied up by long-running requests.

要让GAE具有可伸缩性，就需要减少长时间运行的请求。

GAE promises and delivers scalability but not necessarily raw performance.

GAE承诺并传递可伸缩性，但不一定是原始性能。

Deciding which index to create is a significant burden for GAE developers.

决定要创建哪个索引对于GAE开发人员来说是一个很大的负担。

If you want to build your apps on GAE, there are a few rules you must obey.

如果您想在GAE上建立您的应用程序，则您必须遵守一些规则。

A version for use with the GAE is available-see Resources for the link.

您可以获取一个可用于GAE的版本—参见参考资料中的链接。

Your application should be deployed to GAE successfully after a short while.

您的应用程序稍后就会被成功部署到GAE。

GAE provides excellent scalability as measured by a consistent response time.

GAE提供出色的可伸缩性就像通过一致响应时间所衡量的那样。

Now we have seen how the data gets served from our application running on GAE.

现在我们已经了解了如何通过在 GAE 上运行应用程序处理数据。

In GAE, you can't write files to disk because there's no useable file system.

在 GAE 上，您是无法将文件写入到磁盘的，因为 GAE 根本没有可用的文件系统。

This managed-session object database is transparent to developers - much like GAE.

此托管会话对象数据库对开发人员透明—这很像GAE。

Now, the logging could be viewed using the Logs console in GAE, as shown below.

现在，可以使用GAE中的日志控制台查看日志记录，如下所示。

As it turns out, GAE is an excellent example of a message-oriented middleware system.

事实证明，GAE是面向消息中间件系统的一个很好的例子。

To create each employee, you will use a SOAP service running on GAE, one at a time.

要创建每个员工，您将使用运行在GAE上的一个SOAP服务—一次一个。

Keys in the GAE datastore are also unique, just as they would be in a traditional database.

GAE数据存储中的键也是惟一的，正如在传统的数据库中一样。