GoBridge documentation
GoBridge routes messages between systems that do not speak the same protocol —
MQTT, AWS SQS, Azure Service Bus, RabbitMQ (AMQP 0-9-1), AMQP 1.0 and HTTP —
with durable delivery, dead-letter handling, clustering and observability.
New here? Read Scenario 1: MQTT-to-MQTT first: it
walks a working bridge end to end. Then skim the
Configuration Overview.
Start here
Configuration
| Page |
What it covers |
| Configuration Overview |
Lifecycle, sources, layering, dynamic reconfiguration |
| Configuration Reference |
Field-by-field BridgeConfig reference |
| Routes and Runtime Reference |
Route shape and runtime behaviour |
| Failover Budget |
What exclusive-session failover costs, and what admission checks |
| Programmatic API |
Delivery hooks, the builder, runtime lifecycle |
| Transport Configuration |
Options common to every transport |
| Message Mapping |
What a message looks like on each side: attributes, properties, identity and subject per transport |
| Processors and Stores |
Filter, transform, circuit breaker, tenant |
| Store Backends |
Memory, SQLite and DynamoDB for each store role, and the pairing rules |
| Config Stores |
Where configuration is read from and written to |
Transports
Security and credentials
Clustering
Scenarios
Progressive walkthroughs, from a single MQTT topic to cross-protocol
bridging. See the scenarios index — a few starting points:
Operations
Design decisions
Architecture decision records — the choices behind the delivery model,
clustering, storage and configuration.
Design and contributor documentation (architecture, domain model, glossary,
plugin authoring, testing rules) is written for people changing GoBridge rather
than running it. Each of those documents is a hub in the repository root; where
one grew past what fits in a single sitting, its detail pages live under
internals/ and the hub’s contents table routes to them. See the
repository on GitHub.