Book Image

A Developer's Guide to Building Resilient Cloud Applications with Azure

By : Hamida Rebai Trabelsi
Book Image

A Developer's Guide to Building Resilient Cloud Applications with Azure

By: Hamida Rebai Trabelsi

Overview of this book

To deliver software at a faster rate and reduced costs, companies with stable legacy systems and growing data volumes are trying to modernize their applications and accelerate innovation, but this is no easy matter. A Developer’s Guide to Building Resilient Cloud Applications with Azure helps you overcome these application modernization challenges to build secure and reliable cloud-based applications on Azure and connect them to databases with the help of easy-to-follow examples. The book begins with a basic definition of serverless and event-driven architecture and Database-as-a-Service, before moving on to an exploration of the different services in Azure, namely Azure API Management using the gateway pattern, event-driven architecture, Event Grid, Azure Event Hubs, Azure message queues, FaaS using Azure Functions, and the database-oriented cloud. Throughout the chapters, you’ll learn about creating, importing, and managing APIs and Service Fabric in Azure, and discover how to ensure continuous integration and deployment in Azure to fully automate the software delivery process, that is, the build and release process. By the end of this book, you’ll be able to build and deploy cloud-oriented applications using APIs, serverless, Service Fabric, Azure Functions, and Event Grid technologies.
Table of Contents (18 chapters)
1
Part 1: Building Cloud-Oriented Apps Using Patterns and Technologies
5
Part 2: Connecting Your Application with Azure Databases
13
Part 3: Ensuring Continuous Integration and Continuous Container Deployment on Azure

Exploring non-relational data concepts in Azure

When we start building a new application, we need to think about how to store data. This usually takes the form of a relational database, where data is organized in linked tables and managed using SQL. However, many applications don’t need the rigid structure of a relational database; we can use non-relational storage (commonly known as NoSQL).

Let’s explore some characteristics of non-relational data. Non-relational data doesn’t follow the rules of relational data. In its native form, data can be loaded quickly. If you have unknown data or queries, non-relational data will be more flexible and better than relational data, but it is less good for known data structures and known queries.

Entities have highly variable structures. For example, in a medical appointment database that stores information about patients, a patient can have more than a telephone number, landline, and mobile number. They can add multiple...