利用Azure Cosmos DB构建全球分布式NoSQL应用指南

需积分: 10 155 浏览量更新于2024-07-17 收藏 9.48MB PDF 举报

《Azure Cosmos DB指南》是一本专注于指导开发者利用Azure Cosmos DB构建应用程序的实用手册。Azure Cosmos DB是微软提供的一种全球分布、可扩展性极强且支持多种模型的NoSQL数据库服务，特别适合处理大量数据和实现跨地域应用的需求。本书主要针对C#、JSON、LINQ和.NET Core 2进行讲解，旨在帮助读者掌握如何有效地与这种云数据库进行交互。在学习过程中，作者Gaston C. Hillar和Daron Yöndem首先会引导读者熟悉Azure Cosmos DB的基本操作，包括通过Azure Cosmos DB Emulator编写简单的查询和处理响应。读者将逐渐深入，学会使用更复杂的查询构造技术，这有助于提升对NoSQL数据模型的理解。书中核心内容围绕创建一个完整的C#应用程序展开，该应用将与Azure Cosmos DB集成，让读者了解所需的相关.NET Core 2类和API。通过LINQ（Language Integrated Query）的实践，读者能更好地运用面向对象编程来执行高效查询。同时，还将探讨文档对象模式（POCOs，Plain Old CLR Objects）的应用，进一步强化查询能力。在掌握了Azure Cosmos DB的NoSQL特性后，读者将有能力开发出可扩展、全球化分布和高度响应的应用程序。尽管书中的信息力求准确，但读者需意识到，由于技术的不断发展，部分细节可能会有所变化，因此在实际应用中可能需要结合最新文档进行调整。版权方面，所有内容未经Packt Publishing事先书面许可，不得复制、存储或以任何形式传输，除非用于引用目的。此外，尽管作者和出版商尽力确保信息的准确性，但书中提供的信息并不保证无误，也不承担因使用本书导致的直接或间接损失的责任。在提及商标时，尽管已经尽力确保正确使用，但Packt Publishing并不能对此保证完全准确。

Introduction to NoSQL in Cosmos DB Chapter 1

[ 7 ]

Whenever it is necessary to deploy a new version of the application, we have to make sure

that the migration process is executed and that the underlying database schema has the

required version for the C# code and the ORM configuration. The migration process makes

the necessary changes in the tables and relationships to make it match the ORM mappings.

Hence, a single property that needs to be added to an object and needs to be persisted

generates a cascade of changes in different parts of our application. Of course, there are

many ways of automating the necessary tasks. However, the fact that the tasks are

automated doesn't mean that they aren't required.

Now, let's start thinking about the way in which we are going to work with a Cosmos DB

NoSQL document database. We can start writing our first version of an application with C#

and .NET Core, work with object-oriented programming, and use the provided methods in

the Cosmos DB .NET Core SDK to persist the created objects in the schema-agnostic

document database. There is no ORM between our application code and the NoSQL

database service. We work with objects, we persist them, we retrieve them, and we query

them. We only need to specify serialization and deserialization settings if necessary, but we

don't have to worry about mapping an object to tables and their relationships.

Documents are objects.

Now, seriously, what else do we need to do to create our first version of the application?

We have to learn how to work with the Cosmos DB .NET Core SDK, as well as the

necessary tools for interacting with and managing a Cosmos DB database, in order to be

ready for the first version of the application. We also have to understand the SQL dialect,

which allows us to work against a Cosmos DB document database, in addition to many

scalability and provisioning strategies.

A NoSQL database makes it easier to start working with a first version of

an application compared to the process required with the traditional ORM

and relational database management system combination. We work with

documents, we store documents, we retrieve documents, we query

documents. We don't require complex mappings and translations. We can

work with object-oriented code without adding complex middleware such

as an ORM.

Introduction to NoSQL in Cosmos DB Chapter 1

[ 8 ]

Whenever it is necessary to deploy a new version of an application that is working against

a Cosmos DB NoSQL document database, we don't have to worry about migration

processes. If we need to add a single property to an object, we just add it and persist it in

the schema-agnostic document database. There is no need to run any script that makes

changes to the existing documents. We can continue working with the documents with a

different schema, as they will be able to coexist with the new documents that have a new

schema.

What about queries that work only with the new property? No problem—we can use

properties or keys that don't exist in all the persisted documents; the schema-agnostic

features support this scenario. For example, we can start running queries that check

whether the value of the new property matches some specific criteria after persisting an

object that has the new property.

You might be wondering, "why haven't I been working with NoSQL for the last 10 years?"

There is a simple answer to this question: storage costs were higher and relational database

management systems made it easy to optimize storage use while providing great database

features. However, things have changed, and nowadays, we have new options. Cosmos DB

provides a NoSQL database service that allows us to get up and running very quickly. We

will learn how to create a first version and a second version of an application to simplify

the paradigm shift to the NoSQL way of working with Cosmos DB.

Obviously, as always happens, relational databases will still be great for thousands of

scenarios. However, be sure that the time you invest in learning Cosmos DB features will

allow you to use its services in an application in which you thought that the only choice

was a traditional relational database.

Learning about the main features of Cosmos

Cosmos DB extends the database service that was known as Azure Document DB.

However, it is very important to note that Cosmos DB adds a huge number of features to

the services offered by its predecessor. In fact, Cosmos DB is continuously adding new

features and has quickly become one of the most innovative services found in Azure that

targets mission-critical applications at a global scale.

剩余204页未读，继续阅读

NickMouseLao

粉丝: 0
资源: 12

利用Azure Cosmos DB构建全球分布式NoSQL应用指南

"探秘Azure Cosmos DB：NCF案例演示与全球高性能数据库解决方案

SQL Server数据迁移到Azure Cosmos DB指南

MATLAB接口实现Azure Cosmos DB数据库连接与操作

NCF 的Azure Cosmos DB 演示案例.doc

Orleans.CosmosDB：Azure Cosmos DB的奥尔良提供商

将数据从SQL Server迁移到Azure Cosmos DB

spring-data-cosmosdb：使用Azure Cosmos DB访问数据

Catalogue:带有Azure Cosmos DB的.NET RESTful API

jakarta-nosql-cosmosdb：将Jakarta NoSQL与Cosmos DB一起使用的演示

Azure Cosmos DB 动手实验详解与实践指南

最新资源