Book Image

Hands-On Azure Digital Twins

By : Alexander Meijers
Book Image

Hands-On Azure Digital Twins

By: Alexander Meijers

Overview of this book

In today’s world, clients are using more and more IoT sensors to monitor their business processes and assets. Think about collecting information such as pressure in an engine, the temperature, or a light switch being turned on or off in a room. The data collected can be used to create smart solutions for predicting future trends, creating simulations, and drawing insights using visualizations. This makes it beneficial for organizations to make digital twins, which are digital replicas of the real environment, to support these smart solutions. This book will help you understand the concept of digital twins and how it can be implemented using an Azure service called Azure Digital Twins. Starting with the requirements and installation of the Azure Digital Twins service, the book will explain the definition language used for modeling digital twins. From there, you'll go through each step of building digital twins using Azure Digital Twins and learn about the different SDKs and APIs and how to use them with several Azure services. Finally, you'll learn how digital twins can be used in practice with the help of several real-world scenarios. By the end of this book, you'll be confident in building and designing digital twins and integrating them with various Azure services.
Table of Contents (25 chapters)
1
Section 1: Azure Digital Twin Essentials
4
Section 2: Getting Started with Azure Digital Twins
11
Section 3: Digital Twins Advanced Techniques
19
Section 4: Digital Twin Implementations in Real-world Scenarios

Understanding service limits

It is important to understand that using the services, via APIs and SDKs, is not unlimited. The Azure Digital Twins instance has several types of limits. These types are explained here:

  • Functional Limits: Functional limits are limits that are defined by the ability of the service. Think of the number of instances, models, digital twins, and joins inside a query or the size of a certain message.
  • Rate Limits: These limits are limits of the requests we make to the service. Think of the number of read requests per second. When we try to read more than these limits, we are throttled on the result of the request. One such example is executing queries. When you create a solution, which is used by a lot of people, and the solution is continuously requesting data by querying, you could easily reach the query limit.

Service throttling takes place on additional requests when a certain limit is reached. We will receive the 429 error as a response...