Back to Catalog
Integration
Message Routing
Content-Based Router
Read what is in the message and send it where it belongs based on its content.
Intent & Description
Real-world Use Case
Insurance claims routing — a ClaimSubmitted message is routed based on claimType field. AUTO claims go to auto-claims-service, HEALTH to health-claims-service, PROPERTY to property-claims-service. Same message, three destinations based on content.
Source
📌 TL;DR
Content-Based Router = reads inside the message and decides where it goes. Smart routing based on business data. Keep the rules simple or it becomes a maintenance headache.
Advantages
- Routes based on actual business data — not just message metadata
- Enables a single channel to serve multiple downstream services
- Centralizes conditional routing in one auditable component
- Rules are explicit and easy to document
Disadvantages
- Router must understand message structure — coupling between router and schema
- Complex content-based rules become hard to maintain
- Schema changes in payload require router rule updates
- Performance cost of payload parsing vs header-only routing