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

Querying relationships

This section will explain how we can query relationships by using the JOIN operator. The JOIN operator allows us to join (or combine, as we say) different result sets of digital twins. You can add up to five JOIN operators in one query.

There are some rules that we have to apply when using a JOIN operator. These rules are as follows:

  • We need to specify a name for a result set. That means that we need to replace FROM DIGITALTWINS with, for example, FROM DIGITALTWINS DT. DT, is, in this case, the name of the result set. The name can be anything we want.
  • The query is required to have a $dtId value in the WHERE clause.
  • The SELECT * needs to be replaced with, for example, SELECT DT, RT. DT and RT, in this case, are both result sets. At least one result set or a specific field in a result set is required.

The following query does a JOIN operation between digital twins with a specified relationship called contains. In our current Azure Digital...