Introduction
DRIVR uses a flexible, compact data model that allows you to represent and organize IoT systems and their activities in the cloud. For example, a physical device can be modeled as a Component, while a group of related devices can be modeled as a System.
These entities, collectively referred to as Resources, are accessible through the GraphQL API, and some are also available via the MQTT API.
Review the data model basics and the getting-started guides to understand how to model your prototypes in DRIVR.
Making separate API requests for every change or addition to your data model can be cumbersome, error-prone, and time-consuming, especially when managing multiple domains, environments, or version histories.
To simplify this process, DRIVR provides a Data Import API that lets you upload a YAML representation of your data model. With this API, you can apply batched updates in a single call, making it ideal for CI/CD pipelines. You can also reuse the same YAML file across environments, for example, deploying from staging to production. When stored in version control, this file enables rollbacks and a complete version history of your data model.