[Story 3/3] Tutorial: High-Throughput IoT Telemetry Pipeline with AMQP Workers & AI Diagnostics #14

Open
opened 2026-10-27 14:51:24 +00:00 by crapougnax · 0 comments
Owner

Migrated from GitHub https://github.com/Quatrain/Core/issues/41 (opened by @crapougnax on 2026-09-18).

🎯 Story Overview

As a Distributed Systems & IoT/AI Architect,
I want to build an industrial telemetry acquisition pipeline that decouples sensor frame ingestion via RabbitMQ workers, manages physical device capabilities via MDM ontology, routes data across polyglot backends (PostgreSQL, AMQP, S3), and triggers structured Gemini AI incident diagnoses on threshold breaches,
So that high-frequency edge IoT workloads run asynchronously, resiliently, and sovereignly on on-premise or cloud infrastructure.


📦 Ecosystem Packages

  • @quatrain/mdm (Device Ontology, Hardware Capabilities Matrix)
  • @quatrain/queue & @quatrain/queue-amqp (RabbitMQ Broker, Worker Concurrency)
  • @quatrain/backend & @quatrain/backend-postgres (Device Registry & Telemetry Relational Store)
  • @quatrain/storage & @quatrain/storage-s3 (Cold Storage Telemetry Archiving)
  • @quatrain/ai & @quatrain/ai-gemini (Google Gemini, Schema-Guaranteed Diagnostic JSON)
  • @quatrain/auth-rbac (TarpitManager Anti-Abuse Rate Limiting)

📋 Child Tasks & Implementation Plan

  • #15: feat(example-iot-telemetry): define MDM device ontology and telemetry metric models
  • #16: feat(example-iot-telemetry): configure AMQP RabbitMQ broker with concurrent worker consumers
  • #17: feat(example-iot-telemetry): implement polyglot ObjectUri pipeline and Gemini AI anomaly synthesis
  • #18: docs(example-iot-telemetry): write comprehensive step-by-step tutorial, Containerfile and compose stack

✅ Acceptance Criteria

  1. MDM model supports multi-axis hardware capabilities (radio, power, sensor bus).
  2. RabbitMQ workers ingest sensor frames asynchronously with configurable concurrency (concurrency: 10).
  3. Endpoint protected against sensor flooding via TarpitManager.
  4. Anomaly detection invokes Gemini AI via generateStructured to output guaranteed diagnostic JSON schemas.
  5. Multi-arch Containerfile and docker-compose.yml for local stack (PostgreSQL + RabbitMQ + MinIO).
  6. Full runnable reference application under examples/iot-telemetry-engine.
> Migrated from GitHub https://github.com/Quatrain/Core/issues/41 (opened by @crapougnax on 2026-09-18). ## 🎯 Story Overview **As a** Distributed Systems & IoT/AI Architect, **I want to** build an industrial telemetry acquisition pipeline that decouples sensor frame ingestion via RabbitMQ workers, manages physical device capabilities via MDM ontology, routes data across polyglot backends (PostgreSQL, AMQP, S3), and triggers structured Gemini AI incident diagnoses on threshold breaches, **So that** high-frequency edge IoT workloads run asynchronously, resiliently, and sovereignly on on-premise or cloud infrastructure. --- ### 📦 Ecosystem Packages - `@quatrain/mdm` (Device Ontology, Hardware Capabilities Matrix) - `@quatrain/queue` & `@quatrain/queue-amqp` (RabbitMQ Broker, Worker Concurrency) - `@quatrain/backend` & `@quatrain/backend-postgres` (Device Registry & Telemetry Relational Store) - `@quatrain/storage` & `@quatrain/storage-s3` (Cold Storage Telemetry Archiving) - `@quatrain/ai` & `@quatrain/ai-gemini` (Google Gemini, Schema-Guaranteed Diagnostic JSON) - `@quatrain/auth-rbac` (TarpitManager Anti-Abuse Rate Limiting) --- ### 📋 Child Tasks & Implementation Plan - [ ] #15: `feat(example-iot-telemetry): define MDM device ontology and telemetry metric models` - [ ] #16: `feat(example-iot-telemetry): configure AMQP RabbitMQ broker with concurrent worker consumers` - [ ] #17: `feat(example-iot-telemetry): implement polyglot ObjectUri pipeline and Gemini AI anomaly synthesis` - [ ] #18: `docs(example-iot-telemetry): write comprehensive step-by-step tutorial, Containerfile and compose stack` --- ### ✅ Acceptance Criteria 1. MDM model supports multi-axis hardware capabilities (radio, power, sensor bus). 2. RabbitMQ workers ingest sensor frames asynchronously with configurable concurrency (`concurrency: 10`). 3. Endpoint protected against sensor flooding via `TarpitManager`. 4. Anomaly detection invokes Gemini AI via `generateStructured` to output guaranteed diagnostic JSON schemas. 5. Multi-arch `Containerfile` and `docker-compose.yml` for local stack (PostgreSQL + RabbitMQ + MinIO). 6. Full runnable reference application under `examples/iot-telemetry-engine`.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
quatrain/core#14
No description provided.