About the event
IoT solution development always involves a domain model. When not well-defined this often leads to issues where it needs costly adapted later on. In this event we will show best practices in domain model design for Cumulocity IoT incl. examples which should help you in your solution development process.
Resources
- The Cumulocity IoT Domain Model - Why a domain model is important for IoT solutions
- The Cumulocity IoT Domain Model - How to design a good domain model
- The Cumulocity IoT Domain Model - Application data & Query optimization
- Alarm de-duplication in Cumulocity IoT
- Cumulocity Open API - Cumulocity IoT - OpenAPI Specification
- Cumulocity Documentation Domain Model - Cumulocity IoT's domain model - Cumulocity IoT Guides
- Inventory API - Cumulocity IoT - OpenAPI Specification
- Identity API - Cumulocity IoT - OpenAPI Specification
- Event API - Cumulocity IoT - OpenAPI Specification
- Measurement API - Cumulocity IoT - OpenAPI Specification
- Alarm API - Cumulocity IoT - OpenAPI Specification
- Device Control API - Cumulocity IoT - OpenAPI Specification
- Tenant Options API - Cumulocity IoT - OpenAPI Specification
- Tenant Object API - Cumulocity IoT - OpenAPI Specification
- Audit Records API - Cumulocity IoT - OpenAPI Specification
- Query Language - Cumulocity IoT - OpenAPI Specification
- Device Vendor Requirements - https://github.com/SoftwareAG/cumulocity-self-service-certification/blob/main/docs/vendor-requirements.md
Slides
Best Practices Domain Model Design.pdf (4.3 MB)