Learning About Platform Interfaces and Automation

Objective

After completing this lesson, you will be able to integrate applications using REST Delivery Points, connect microservices, and manage hybrid event messaging workloads with centralized telemetry and monitoring.

Application Integration and Microservices Patterns

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.

Fundamentals of REST

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.

Platform Operations, Monitoring, and Observability

Operating mission-critical event meshes across hybrid environments requires continuous monitoring and deep visibility into asynchronous message flows. This concept topic examines real-time health metrics, automated alerting, and end-to-end distributed tracing.

Real-Time Health and Performance Monitoring

The Cloud Console provides continuous operational monitoring to keep broker clusters performing reliably. Operations teams track essential performance metrics in real time:

Broker & Cluster Health

Tracks CPU usage, memory consumption, message spool capacity, and High Availability (HA) status across active and standby nodes.

Queue & Connection Metrics

Monitors active client connections, queue depths, unacknowledged message counts, and ingress/egress throughput rates.

Alerting & Notification Rules

Automated alerts can be configured to notify administrators via email or webhooks when resource limits or error thresholds are breached.

End-to-End Distributed Tracing with OpenTelemetry

In complex event-driven systems, tracing an asynchronous message across multiple microservices is critical for operational visibility and troubleshooting. SAP Integration Suite, advanced event mesh natively supports Distributed Tracing based on OpenTelemetry standards by automatically attaching and preserving trace context headers as messages flow through the event mesh. This generated telemetry data, including spans, execution timings, and dynamic routing paths, can be exported directly to enterprise observability platforms such as Datadog, Dynatrace, or Splunk. Consequently, operations teams can visualize complete end-to-end event journeys, rapidly pinpoint processing bottlenecks, and resolve failed message deliveries across distributed hybrid landscapes.

End-to-End Tracing