Grid与Cloud数据库管理：2011版概述

需积分: 10 156 浏览量更新于2024-07-30 收藏 4.86MB PDF 举报

"Grid and Cloud Database Management 2011版.pdf" 《Grid and Cloud Database Management》是由Sandro Fiore和Giovanni Aloisio编辑的一本专业书籍，主要探讨了网格和云数据库管理的理论与实践。两位编辑均来自意大利莱切大学工程学院创新工程系，并在欧洲地中海气候变化中心（CMCC）任职。这本书的国际标准书号（ISBN）为978-3-642-20044-1，电子书号为978-3-642-20045-8，由Springer出版社出版。该书深入研究了在网格和云计算环境下的数据库管理系统，这是一个与计算机网络、分布式系统和数据存储高度相关的领域。根据美国计算机学会（ACM）1998年的分类体系，这本书涵盖了C.2（计算机系统组织——分布式、并行和集群计算）、H.2（信息存储和检索——数据库系统）、H.3（信息存储和检索——信息系统）以及J.2和J.3（计算机应用——信息处理——数据库和文件系统、网络应用）的相关内容。网格和云数据库管理涉及如何在大规模分布式环境中高效、安全地存储和处理数据。网格计算允许资源的共享和协同工作，而云数据库则利用虚拟化技术提供按需服务的模式。此书可能详细讨论了以下知识点： 1. **网格计算基础**：包括网格架构、资源调度和任务分配策略，以及网格中的数据管理和通信协议。 2. **云计算模型**：如IaaS（基础设施即服务）、PaaS（平台即服务）和SaaS（软件即服务），以及它们在数据库服务中的应用。 3. **云数据库设计**：讨论了云环境下的数据库架构，如分布式数据库、并行数据库和弹性数据库设计。 4. **数据存储和访问**：涵盖数据分片、复制、缓存策略，以及在大规模分布式环境中的数据一致性保证。 5. **安全性与隐私**：包括数据加密、访问控制、身份验证和审计机制，以及在网格和云环境中的隐私保护策略。 6. **性能优化**：探讨查询优化、负载均衡、资源调度等技术，以提高系统性能和响应时间。 7. **容错与可靠性**：介绍故障检测、恢复机制和高可用性设计，确保服务的连续性和数据的完整性。 8. **网格与云的互操作性**：讲述如何在不同计算模型之间实现数据和服务的无缝迁移和互操作。 9. **案例研究与最佳实践**：可能包含实际应用案例，展示如何在真实场景中实施网格和云数据库管理系统。通过阅读本书，读者可以获取到网格和云数据库管理的最新研究成果，以及在实际项目中实施这些技术的方法和挑战。对于从事分布式计算、云计算和大数据管理的IT专业人士来说，这是一份宝贵的参考资料。

1 Open Standards for Service-Based Database Access and Integration 5

1.2 The WS-DAI Family of Speciﬁcation

1.2.1 Overview

The relationship between the WS-DAI (Web Services Database Access and Integra-

tion Services) family of speciﬁcations is schematically illustrated in Fig. 1.1.These

provide a set of message patterns and properties for accessing various types of data.

A core speciﬁcation, the WS-DAI document [6], deﬁnes a generic set of interfaces

and patterns which are extended by speciﬁcations dealing with particular data

models: WS-DAIR for relational databases [7], WS-DAIX for XML databases [8]

and WS-DAI-RDF(S) for Resource Description Framework (RDF) databases [9].

In WS-DAI, a database is referred to as a data resource. A data resource

represents any system that can act as a source or sink of data. It has an abstract

name which is represented by a URI and an address which shows the location of a

resource. A data access service provides properties and interfaces for describing and

accessing data resources. The address of a resource is a web service endpoint such

as an EndPointReference (EPR) provided by the WS-Addressing [10] speciﬁcation.

A WSRF data resource provides compatibility with the WS-Resource (WSRF) [4]

speciﬁcations. A consumer refers to the application or client that interacts with the

interfaces provided by a data resource.

An important feature introduced by WS-DAI is the support for indirect access

patterns. Typically, web services have a request-response access pattern – this is

referred to as direct data access – where the consumer will receive the requested

data in the response to a request, typically a query, made to a data access service. For

example, passing an XPathQuery message to an XML data access service will result

in a response message containing a set of XML fragments. An operation that directly

inserts, updates or deletes data through a data access service also constitutes a direct

data access. For example, passing an SQL insert statement to a data access service

WS-DAI

Message patterns

Core Interfaces

WS-DAIX

XML Access

WS-DAI-RDF(S)

RDF Access

WS-DAI-RDF(S)-Ontology

Ontology Access

WS-DAI-RDF(S)-Query

Query Access

WS-DAIR

Relational Access

Fig. 1.1 The WS-DAI family of speciﬁcations

6 S. Lynden et al.

will result in a response message indicating how many tuples have been inserted.

For indirect data access, a consumer will not receive the results in the response

to the request made to a data access service. Instead, the request to access data is

processed with the results being made available to the consumer indirectly as a new

data resource, possibly through a differentdata service that supports a different set of

interfaces. This is useful, for instance, to hold results at the service side minimising

any unnecessary data movement. The type and behaviour of the new data resource

are determined by the data access service and the conﬁguration parameters passed

in with the original request. This indirect access behaviour is different from the

request-response style of behaviour found in typical web service interactions.

1.2.2 The Core Speciﬁcation (WS-DAI)

The WS-DAI speciﬁcation, also referred to as the core speciﬁcation, groups

interfaces into the following functional categories:

• Data description: Metadata about service and data resource capabilities.

• Data access: Direct access interfaces.

• Data factory: Indirect access interfaces.

It is important to note that data access and data factory operations wrap existing

query languages to specify what data is to be retrieved, inserted or modiﬁed in the

underlying data resources. The DAIS speciﬁcations do not deﬁne new query lan-

guages nor do they do any processing on the incoming queries nor do they provide

a complete abstraction of the underlying data resource – for instance, you have to

know that the data service you are interacting with wraps a relational database to

send SQL queries to it. The beneﬁt of DAIS is that it provides a set of operations

that will function on an underlying data resource without requiring knowledge of the

native connection mechanisms for that type of database. This makes it easier to build

client interfaces that will use DAIS services to talk to different types of databases.

These interface groupings provide a framework for the data service interfaces

and the properties that describe, or modify, the behaviour of these interfaces that

can then be extended to deﬁne interfaces to access particular types of data, as is

done by the WS-DAIR, WS-DAIX and WS-DAI-RDF(S) documents.

1.2.2.1 Data Description

Data Description provides the metadata that represents the characteristics of the

database and the service that wraps it. The metadata are available as properties that

can be read and sometimes modiﬁed. If WSRF is used, the WSRF mechanisms can

be used to access and modify properties otherwise operations are available to do this

for non-WSRF versions of WS-DAI. For instance, the message GetDataResource-

PropertyDocument will retrieve metadata that includes the following information:

1 Open Standards for Service-Based Database Access and Integration 7

1. AbstractNames: A set of abstract names for the data resources that are available

through that data services. Abstract names are unique and persistent name for a

data resource represented as URIs.

2. ConcurrentAccess: A ﬂag indicating whether the data service provides concur-

rent access or not.

3. DataSetMap: Can be used to retrieve XML Schema representing the data formats

that the data service can return the results in.

4. LanguageMap: Shows the query languages that are supported by the data service.

Note that DAIS does not require the service to validate the query language that is

being used; improper languages will be detected by the underlying data resource.

5. Readable/Writable: A ﬂag indicating whether the data service provides read and

write capabilities to the resource. For instance, if the service were providing

access to a digital archive it would clearly only have read-only access. This

property is meant to describe the underlying characteristics of the data resource

rather than authorization to access the resource.

6. TransactionInitiaton: Information about the transactional capabilities of the

underlying data resource.

Using this information, a user can understand the database and service capabili-

ties provided by that data service. The property set can be extended to accommodate

particular properties pertaining to access to speciﬁc types of data, for example,

relational, XML and RDF.

1.2.2.2 Data Access

Data access collects together messages that can directly access or modify the data

represented by a data access service along with the properties that describe the

behaviour of these access messages, as illustrated in Fig. 1.2, which depicts a use

case where the WS-DAIR interfaces are used.

Consumer

Database

Data Access Service

SQLAccess

Relational

Database

SQLResponse

SQLExecute ( Data

ResourceAbstractName,

DatasetFormatURI,

SQLExpression )

SQLDescription:

Readable

Writeable

ConcurrentAccess

TransactionInitiation

TransactionIsolation

Etc.

Fig. 1.2 Data access example

8 S. Lynden et al.

In this example, the data access service implements the SQLAccess messages

and exposes the SQLDescription properties; more details about the interface and

corresponding properties can be found in [7]. A consumer uses the SQLExecute

message to submit an SQL expression. The associated response message will

contain the results of the SQL execute request. When the SQL expression used is a

SELECT statement, the SQL response will contain the data in a RowSet message

serialized using an implementation-speciﬁc data format, for example the XML

WebRowSet [11].

1.2.2.3 Data Factory

Factory messages create a new relationship between a data resource and a data

access service. In this way, a data resource may be used to represent the results of a

query or act as a place holder where data can be inserted. A data factory describes

properties that dictate how a data access service must behave on receiving factory

messages. The factory pattern may involve the creation of a new data resource and

possibly the deployment of a web service to provide access to it (though existing

web services can be re-used for this purpose – DAIS does not specify how this

should be implemented). The WS-DAI speciﬁcation only sets the patterns that

should be used for extensions to particular types of data.

This ability to derive one data resource from another, or to provide alternative

views of the same data resources, leads to a collection of notionally related data

resources, as illustrated in Fig. 1.3, which again takes an example from the WS-

DAIR speciﬁcation. The database data access service in this example presents an

SQLFactory interface. The SQLExecuteFactory operation is used to construct a new

derived data resource from the SQL query contained in it. These results are then

made available through an SQLResponseAccess interface which may be available

through the original service or as part of a new data service. Access to the RowSet

resulting from the SQL expression executed by the underlying data resource is made

available through a suitable interface, assuming that the original expression contains

a SELECT statement.

The RowSet could be stored as a table in a relational database or in a form decou-

pled from the database. DAIS does not specify how this should be implemented but

the implementation does have a bearing on the properties of ChildSensitiveToParent

and ParentSensitiveToChild which indicate whether changes in the child data affect

the parent data or changes in the parent data affect the child data, respectively. The

RowSet results are represented as a collection of rows via a data access service

supporting the SQLResponseAccess collection of operations that allow the RowSet

to be retrieved but does not provide facilities for submitting SQL expressions via

the SQLAccess portType.

The Factory interfaces provide a means of minimising data movement when it is

not required in addition to an indirect form of third party data delivery: consumer A

creates a derived data resource available through some speciﬁed data service whose

reference can be passed on to consumer B to access.

剩余363页未读，继续阅读

敖日格勒

粉丝: 21
资源: 21

Grid与Cloud数据库管理：2011版概述

Building.Database.Clouds.in.Oracle.12c.0134310861

oracle grid infrastructurehecrsd

怎么点云体素化用代码演示出来如import open3d as o3d # 读取点云文件 pcd = o3d.io.read_point_cloud("cloud.ply") # 网格大小为0.05的体素化 voxel_grid = o3d.geometry.VoxelGrid

def point_cloud_to_voxel(point_cloud, voxel_resolution): voxel_grid = np.zeros(voxel_resolution, dtype=np.int32)转换为c++代码

怎么使用pointcloud库

最新资源