Book Image

Data Modeling for Azure Data Services

By : Peter ter Braake
Book Image

Data Modeling for Azure Data Services

By: Peter ter Braake

Overview of this book

Data is at the heart of all applications and forms the foundation of modern data-driven businesses. With the multitude of data-related use cases and the availability of different data services, choosing the right service and implementing the right design becomes paramount to successful implementation. Data Modeling for Azure Data Services starts with an introduction to databases, entity analysis, and normalizing data. The book then shows you how to design a NoSQL database for optimal performance and scalability and covers how to provision and implement Azure SQL DB, Azure Cosmos DB, and Azure Synapse SQL Pool. As you progress through the chapters, you'll learn about data analytics, Azure Data Lake, and Azure SQL Data Warehouse and explore dimensional modeling, data vault modeling, along with designing and implementing a Data Lake using Azure Storage. You'll also learn how to implement ETL with Azure Data Factory. By the end of this book, you'll have a solid understanding of which Azure data services are the best fit for your model and how to implement the best design for your solution.
Table of Contents (16 chapters)
1
Section 1 – Operational/OLTP Databases
8
Section 2 – Analytics with a Data Lake and Data Warehouse
13
Section 3 – ETL with Azure Data Factory

Creating a data lake filesystem

A storage account is a container resource for multiple different services that you can implement. The first step is to tell the storage account what you want to create. The four services that are part of a storage account are as follows:

  • Queues
  • Tables
  • File shares
  • Containers

You can see a tile for each of these options on the Overview blade as shown in Figure 10.8:

Figure 10.8 – Storage account Overview blade

Queues enable application developers to set up the asynchronous processing of events by having an application put messages in a queue and having another system process these messages. The Tables feature is a NoSQL key-value database. File shares are used when you have multiple Azure virtual machines that need access to the same files using the Server Message Blocks (SMB) protocol. When implementing a data lake, you need to create one or more containers. Here's the fourth option:

...