如果您的应用系统是在公司和银行之间传输财务数据的后端系统，那么，您的用户可能是一些公司的内部部门或银行。
If your application is a back-end system for transferring financial data between your company and a bank, then your user is probably some internal group in your company or the bank.
需要缓存数据库或其他后端数据存储区中的数据，并需要以其他方式无法达到的速度访问这些数据？
Need to cache data from a database or other backend data store that needs to be accessed at speeds that would otherwise be unattainable?
第4行代码将文档更改保存到后端数据存储。
Line 4 saves the document changes to the backend data store.
实际的数据验证是后端应用程序的职责。
Actual data verification will be the responsibility of the backend applications.
单一可执行文件将语言环境信息传递给后端数据系统。
The single executable passes the locale information to the back-end data system.
以这种方式序列化所有后端数据是可行的。
大多数企业已经可以熟练地对用户使用VPN连接来获取后端数据。
Most enterprises are already comfortable with using VPN connections with their users to get to back-end data.
最后，后端实现对数据的物理存储。
Finally, the back end implements the physical storage for data.
清单3是从后端数据存储获取文档的示例。
Listing 3 is an example of getting documents from the backend data store.
例如，业务组件撤销对后端数据的访问。
For example, the business component might revoke access to the back end data.
我们并不从Rails使用这些特性；我们只使用Rails提供数据服务后端。
We will not use those features from Rails; we will just use it to provide a data service back end.
因此，提取后端数据的逻辑包装在Work对象中。
Therefore, the logic of fetching the back-end data is wrapped in a Work object.
业务组件代码必须能够将这个标识符映射到其后端数据中。
The business component code must be able to map this identifier to its back end data.
一个备份包含角色、社区成员、应用程序数据、通常还有业务组件的后端数据。
A backup contains roles, community members, application data, and, usually, the back end data of the business components.
这些对象表示了需要从后端数据结构中删除的数据。
These objects represent data that needs to be removed from backend data structure.
在这些分层解决方案中，有一个内存中的数据库缓存功能，作为后端数据库的前端。
An in-memory database caching capability ACTS as a front end to a back-end database in these tiered solutions.
通过前面所描述的数据绑定机制可以实现该操作，只不过这次实际上是绑定到后端数据元素。
This is done through the data binding mechanism described previously, only this time you are actually binding to backend data elements.
数据支持确保检索数据与更新数据的应用程序，在后端数据库的当前状态下，被同时保存。
Data persistence ensures that applications that retrieve and update data are kept in sync with the current state of the back-end database.
应用程序通过存储过程直接访问后端数据源。
Applications directly access a back-end data source through stored procedures.
为示例应用创建数据库后端。
这会减少对后端数据库的请求数量。
This reduces the number of requests to the backend database.
后端数据系统找到正确的数据，并将其发送回单一可执行文件。
The back-end data system finds the correct data, and sends it back to the single executable.
数据库服务器-后端数据库。
资源处理程序仅包含少量代码，用于处理输入数据，并且ZRM完全隐藏了与后端数据库的交互。
The resource handlers contain very little code in order to process incoming data, and the ZRM completely hides interactions with the back end database.
存储该数据是为了优化性能，因为存储原始数据的后端系统可能很慢，或者与后端系统的连接很慢或者不稳定。
This data is stored in order to optimize performance, because the backend system that stores the original data might be slow, or there is a slow or unstable connection to that backend system.
数据仲裁程序处理与后端数据源交互的复杂性并应用所作的修改。
The data mediator handles the complexities of interacting with the back-end data source to apply the changes.
如果向查询提供数据的后端数据源断开了，并且优化器选择使用MQT来满足查询，那么查询将会执行。
If a back-end data source that provides data to a query is down and the optimizer chooses to satisfy the query using MQTs, the query will be executed.
模拟数据访问对象实际上模拟后端数据存储。
Simulated data access objects essentially simulate a back-end datastore.
相对于数据库后端和网站前端的分离，该商业模型意味着更广阔意义上的内容与展现分离。
This business model implies the separation of content and presentation in a much broader sense then that of database back end – website front end only.
存储库由一个关系数据库提供后端支持。
应用推荐