Back to Catalog
Integration
Message Routing
Dynamic Router
Routing rules that can be changed at runtime — no redeploy needed.
Intent & Description
Real-world Use Case
A/B testing for message processing — Dynamic Router sends 80% of checkout messages to checkout-service-v1 and 20% to checkout-service-v2. Ratio is adjusted live via the router’s control API without any service restarts.
Source
📌 TL;DR
Dynamic Router = routing rules as config, not code. Change where messages go at runtime. Powerful for A/B testing and operational flexibility. Guard against bad rule updates.
Advantages
- Routing changes without deployments — huge ops flexibility
- Enables A/B testing, gradual rollouts, and feature flags at the routing layer
- Operators can react to incidents by changing routes instantly
- Rule management can be delegated to non-developer team members
Disadvantages
- External rule store becomes a critical dependency of the router
- Rules must be validated before applying — bad rules can misroute all traffic
- Runtime rule changes can be hard to audit and rollback
- More complex to implement and test than static routing