Modern enterprise landscapes require flexible integration patterns that connect traditional applications, cloud-native microservices, and external web services. This concept topic explores how REST Delivery Points (RDPs) push events to HTTP endpoints and how multi-protocol support enables seamless interaction across diverse technologies.
Fundamentals of REST Delivery Points (RDP)
A REST Delivery Point (RDP) is an outbound connector hosted directly within an Event Broker Service that bridges persistent queues to external HTTP/REST endpoints. Instead of requiring target applications to poll queues continuously, an RDP acts as an active HTTP client. When an event arrives in an associated queue, the broker automatically wraps the message payload into an HTTP POST request and delivers it directly to the target system's REST API or webhook endpoint.
To ensure reliable event delivery to external web services, RDPs integrate directly with the broker's persistent queueing infrastructure. If a target service experiences downtime or returns HTTP errors, the broker retries delivery based on configurable retry delay interval. If the endpoint remains unreachable after maximum retry attempts, the event is safely moved to a Dead-Message Queue (DMQ) for inspection - provided a DMQ has been configured on the associated queue beforehand.

Multi-Protocol Support and Microservices Decoupling
SAP Integration Suite, advanced event mesh provides native multi-protocol support, allowing applications to publish and consume messages using their preferred protocol without custom adapter code:
- Protocol Interoperability
- Applications communicating via MQTT (IoT/mobile), AMQP 1.0 (enterprise cloud services), REST/HTTP, or SMF/Solace Web Messaging (Solace-native protocol) can seamlessly exchange messages with one another.
- Spatial & Temporal Decoupling
- Publish/Subscribe (Pub/Sub) messaging decouples producers and consumers. Producers publish events without needing destination network details, and messages are buffered safely in queues if consumers are temporarily offline.
- Dynamic Workload Scaling
- Multiple microservice instances can share queue processing workloads, allowing teams to scale consumer applications independently based on event traffic volume.
