Video source
A suitable camera or video input.
Compute node
Media acquisition and inference.
Master services
Kafka consumers, events and evidence.
Operator / API
Review or agreed external delivery.
Reference topology. Actual services and network boundaries are delivery-specific.
User request path
The browser connects over HTTPS. Nginx serves the React client and forwards API requests. The REST bridge routes calls to business services through gRPC or Kafka. Authentication and access control must apply to APIs and entity visibility as well as menu items.
Master node
The single-master reference topology groups UI, API, Kafka, camera/event/user/role services, audit, decisions, counters, reporting, alerts, configuration and primary storage. Multiple processes may implement a domain; use supported contracts rather than direct container access.
Compute nodes
Compute nodes acquire video, manage media, execute models and form inference results. Camera allocation, model storage, snapshots and image services support this path. Monitoring and pushgateway components expose operating state. Scaling depends on cameras, frame rates and model cost.
Two transport paths
| Transport | Role | Diagnostic focus |
|---|---|---|
| HTTP / gRPC | Synchronous request and response | Authentication, request schema, timeout and service availability |
| Kafka | Events, entity changes, heartbeat and inference output | Topic configuration, consumers, lag and repeated delivery |
Data and media path
Inference results reach master-node consumers through Kafka. Event services filter and persist records and associate them with media. The application then exposes results to operators or external systems. Diagnose each stage when the final card or report is incomplete.
Network and identity
The actual addresses, ports, TLS termination, directory integration and node count are defined in the delivery. AD, Kerberos or LDAPS may be configured where included; do not assume a specific identity provider.
Acceptance route
Test a permitted user request and a known video event separately. Then verify that the event has the intended source, time, evidence and recipient. Confirm least-privilege access and fault handling.
Reference service ports
These are typical internal service ports from the reference topology, not a list of ports to expose publicly. The delivery’s network policy determines which segments may reach them; confirm the actual configured values.
| Component / protocol | Typical use | Port in the reference diagram |
|---|---|---|
| HTTPS | Web interface and external API | 443 |
| HTTP / gRPC | UI, gateway and internal calls | 80 / 3000 |
| Apache Kafka | Inter-service messages | 9092 |
| PostgreSQL | Operational and geographical data | 5432 |
| Redis | Sessions, cache and operational state | 6379 |
| MinIO S3 API | Images, video and files | 9000 |
| Prometheus | Metric collection | 9090 |
| Grafana | Metrics and dashboards | 3000 |
| Loki | Log collection and aggregation | 3100 |
For synchronous requests, inspect the service response and gRPC deadline. For asynchronous processing, confirm publication to the expected Kafka topic, consumer lag and handler errors. An HTTP success does not establish that the event and its evidence were stored.