Book Image

Azure Data Engineering Cookbook

By : Ahmad Osama
Book Image

Azure Data Engineering Cookbook

By: Ahmad Osama

Overview of this book

Data engineering is one of the faster growing job areas as Data Engineers are the ones who ensure that the data is extracted, provisioned and the data is of the highest quality for data analysis. This book uses various Azure services to implement and maintain infrastructure to extract data from multiple sources, and then transform and load it for data analysis. It takes you through different techniques for performing big data engineering using Microsoft Azure Data services. It begins by showing you how Azure Blob storage can be used for storing large amounts of unstructured data and how to use it for orchestrating a data workflow. You'll then work with different Cosmos DB APIs and Azure SQL Database. Moving on, you'll discover how to provision an Azure Synapse database and find out how to ingest and analyze data in Azure Synapse. As you advance, you'll cover the design and implementation of batch processing solutions using Azure Data Factory, and understand how to manage, maintain, and secure Azure Data Factory pipelines. You’ll also design and implement batch processing solutions using Azure Databricks and then manage and secure Azure Databricks clusters and jobs. In the concluding chapters, you'll learn how to process streaming data using Azure Stream Analytics and Data Explorer. By the end of this Azure book, you'll have gained the knowledge you need to be able to orchestrate batch and real-time ETL workflows in Microsoft Azure.
Table of Contents (11 chapters)

Configuring the development, test, and production environments

A typical software development environment consists of three environments, development, test (or staging), and production. A development environment is where developers create and unit-test the code; in our case, Azure Data Factory pipelines.

When the development is complete, the pipeline is deployed (moved) to the test environment. In the test environment, testing teams perform tests to validate the pipeline against the business requirements. Any bugs raised are noted and passed on to the developers. The developers then fix the bugs in the development environment and push the changes to the test environment. This goes on until the pipeline passes all of the validation and testing. The pipeline is then pushed to the production environment where it works on the actual data.

In some cases, there can be additional environments such as performance testing, which can be used to performance-test the pipeline before it is...