HiveMQ Documentation HiveMQ Documentation
Get HiveMQ
Home
HiveMQ Platform
Getting Started HiveMQ Control Center HiveMQ Extension Developer Guide HiveMQ REST API HiveMQ Upgrade Guides
HiveMQ Enterprise Extensions
HiveMQ Enterprise Bridge Extension HiveMQ Enterprise Data Lake Extension HiveMQ Enterprise Distributed Tracing Extension HiveMQ Enterprise Extension for Amazon Kinesis HiveMQ Enterprise Extension for Google Cloud Pub/Sub HiveMQ Enterprise Extension for Kafka HiveMQ Enterprise Extension for Microsoft SQL Server HiveMQ Enterprise Extension for MongoDB HiveMQ Enterprise Extension for MySQL HiveMQ Enterprise Extension for PostgreSQL HiveMQ Enterprise Extension for Snowflake HiveMQ Enterprise Security Extension
HiveMQ Cloud HiveMQ Edge HiveMQ Data Hub HiveMQ Platform Operator HiveMQ Swarm

Version:

latest 4.28 4.9 4.5 3.4
  • HiveMQ Data Hub
    • Introduction
      • Features
      • Licensing
        • Trial Mode
    • Quick Start Guide
      • Requirements
      • Installation
      • Configuration
      • Quick Start Control Center
        • Add Schema
        • Add a Data Policy
      • Quick Start REST API
        • Add Schema
          • JSON Schema
          • Protobuf
        • Add a Data Policy
        • Test Your Setup
        • Delete a Policy
      • Next Steps
    • Schemas
      • Control Center
      • REST API
        • Create a Schema
        • Delete a Schema
        • Get a Schema
    • Transformations
      • JavaScript
      • Transformation Scripting
        • Transformation API
          • Publish Object
            • Example Publish Object
          • Context Object
        • Script Requirements
        • Runtime Considerations
        • Example Transformations
          • Add a payload field
          • Restructure message payload
          • Compute payload field
          • Rename payload field
    • Policies
      • Data Policies
        • Control Center
        • REST API
          • Create a Policy
          • Delete a Policy
          • Get a Policy
        • Matching in Data Policies
          • Topic-based Matching
      • Behavior Policies
        • Control Center
        • REST API
        • Matching in Behavior Policies
          • Client ID- based Matching
    • Validation
      • Data Validation
        • Schema-based Validation
    • Behavior Models
      • MQTT Events Model
        • Example MQTT Events Model
      • Publish Duplicate Model
        • Example Publish Duplicate Model
      • Publish Quota Model
        • Example Publish Quota Model
    • Actions
      • Actions in Data Policies
      • Transformations in Data Policies
        • Transformations in Data Policies
        • Transformation Syntax
        • Deserialization & Serialization
          • Example action pipeline
      • Actions in Behavior Policies
      • Functions
        • Non-terminal Functions
          • System.log
          • Metrics.Counter.increment
          • Mqtt.UserProperties.add
          • Serdes.deserialize
          • Serdes.serialize
        • Terminal Functions
          • Delivery.redirectTo
          • Mqtt.disconnect
      • String Interpolation
    • Modules
      • Module Lifecycle
      • HiveMQ Modules
      • Create Custom Module
      • Import Custom Modules
      • Custom Registries
      • Module Specification
        • Module Files and Parameters
          • Index JSON File
          • Variables JSON File
    • Metrics
    • Use Cases
      • Data Validation Use Cases
  • HiveMQ Data Hub
  • Use Cases

HiveMQ Data Hub Use Cases

Browse the informative HiveMQ Policy Cookbooks repository on GitHub for additional use stories and code samples.

Data Validation Use Cases

Our collection of user stories for HiveMQ Data Hub data validation highlight practical ways to use schemas and polices in detail:

  • A policy and schema that enforces that all incoming data packets are valid JSON.

  • Multiple Protobuf policies on different topics for incoming sensor data.

  • Accept multiple possible schemas on a single topic for location data.

  • Ensure messages follow at least one version of a schema and redirect legacy versions to a different topic.

  • Updating an existing policy to use a different schema.

  • A policy that enforces that incoming packets match multiple JSON schemas simultaneously.

Imprint