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

Scope

When setting up a database, you need to know and understand the data you are going to store. You also need to decide on what data is relevant to you and what you are not going to store. You can perform an entity analysis to both define what is relevant to you and understand which parts of the data are relevant. Entity analysis also provides you with an insight as to how complex your data is, which provides you with crucial insights into the risks and timings of your project.

Entity analysis is a top-down approach that provides an initial, high-level view of what our database will look like. Lots of details about the database and the data to be stored will be missing. Along with these details, a lot of the complexity will still be missing. But performing entity analysis enables us to learn about the intended database. We will get a feel for what should and should not be a part of the database. We might even still need to get a first impression of how complex the project at...