Keep ingress and recovery ownership clear
Reuse nginx connection and TLS operations while keeping shared message state and external delivery behind explicit process boundaries.
If your team already operates nginx for TLS, listeners and routing, device traffic can use that same operational boundary. MQTT still needs shared sessions, delivery ownership and a recoverable store when the application requires durability.
Keep connection work bounded
nginx owns inbound TCP/TLS and HTTP Upgrade. Modules parse and validate bounded protocol input, extract credentials and enforce the configured admission boundary. Reviewable configuration and native checks fit the existing nginx deployment process.
Give shared state a local owner
nginx workers are separate processes. The local broker process owns shared sessions, subscriptions, routing, message state, durable replay and readiness. Explicit local rings connect the workers and authority. Container namespace, generation and writer-term checks make that ownership inspectable.
Keep external delivery observable
The bridge process hosts destination clients and customer adapters. It owns bounded retry, backpressure and replay while each configured target has an isolated worker. The application still needs a declared commitment point and provider receipt; broker acknowledgement alone leaves external work unresolved.
Choose the tier from the actual persistence, integration and operating requirements. Use Get Start for configuration and verification, Build for a custom destination, and the measurement guide for the conditions behind the published operating points.