What integration surfaces does the layer expose?

Three integration surfaces: SAP-native (OData, BAPI, RFC, IDoc), layer-native (REST, events, webhooks), and observability (metrics, traces, logs). Every surface uses standard interfaces.

How are errors and retries handled?

Standard retry policies with exponential backoff. Idempotency keys prevent double-writes. Dead-letter queues preserve failed events for manual replay. Every error is logged with full context.

What observability does the layer provide?

Metrics, traces, and logs exposed through standard observability interfaces. Key metrics include order throughput, reconciliation drift, error rates, and latency. The drift meter that runs on the coexistence page is one of the standard observability signals.

Phase 3 · Node Layer 16 · Integration

Standard interfaces.
Full observability. End-to-end traceability.

The integration surface has three tiers: SAP-native interfaces (OData, BAPI, RFC, IDoc), layer-native interfaces (REST, events, webhooks), and observability (OpenTelemetry metrics, traces, logs). Standard retry policies. Idempotency keys. Dead-letter queues. 99.95% uptime commitment. Every event traceable from intake to ack.

SAP-native only Open contracts OpenTelemetry 99.95% uptime Zero proprietary bridges

API

SAP-Native

OData · BAPI · RFC · IDoc

Standard SAP interfaces

EVT

Layer-Native

REST · Events · Webhooks

Open contracts

OBS

Observability

Metrics · Traces · Logs

OpenTelemetry-compatible

The Surface

Three tiers. Fifteen endpoints.
Every one a standard interface.

Click any endpoint to see the interface contract. Every endpoint is a standard interface. Every contract is documented. Nothing is proprietary.

Integration Surface · Live

SAP-native Layer-native Observability

SAP-Native

Tennant → SAP

GET /sap/odata/v4/Orders({id})

GET /sap/odata/v4/Signals

POST /sap/bapi/SALESORDER_CREATE

RFC Z_RECONCILE_LAYER_ORDERS

IDOC ORDRSP · order.placed

Layer-Native

External → Layer

POST /layer/v1/orders

GET /layer/v1/orders/{id}/status

SSE /layer/v1/events/stream

WEBHOOK order.status.changed

WEBHOOK reconcile.drift.detected

Observability

Monitoring → Layer

OTLP layer.metrics.*

OTLP layer.traces.*

OTLP layer.logs.*

GET /healthz · /readyz

GET status.leadreadysite.com

GET · OData · SAP-Native

/sap/odata/v4/Orders({id})

Read the authoritative order status from SAP. Standard OData v4 with ETag-based optimistic concurrency. Reads only — the layer never writes to this endpoint. Used by the reconciliation loop to detect state divergence.

GET /sap/odata/v4/Orders('PM-847291')/Status
Authorization: Bearer <oauth2>
If-None-Match: "etag-v41"

→ 200 OK
{
  "order_id": "PM-847291",
  "status": "shipped",
  "last_updated": "2026-10-12T16:48:33Z",
  "etag": "etag-v42"
}

The Trace

Watch an order flow through five hops.

Every order traces through five hops from intake to ack. Each hop has a timestamp. Every trace is preserved. This is what end-to-end traceability looks like in production.

Integration Trace · Running

Layer Intake

Order received

ADP

SAP Adapter

Translation

SAP

SAP System

Write via BAPI

VAL

Response

Validation

ACK

Reconcile

Ack + close

16:48:31.042 POST /layer/v1/orders · order PM-847291 accepted

16:48:31.128 Adapter translation · idempotency_key=PM-847291-v41

16:48:32.011 BAPI_SALESORDER_CREATEFROMDAT2 · 201 Created · SALESDOCUMENT 0000048291

16:48:32.298 Response validation · schema OK · ETag captured

16:48:32.514 Reconcile ack · drift 0 · order closed

Every hop is timestamped. Every trace is preserved. Total round trip under 1.5 seconds.

Observability

Four live signals. Continuous.

Four signals are continuously measured: uptime, drift, latency p95, and error rate. Each is exposed through standard observability interfaces. Each is externally consumable — no proprietary dashboards required.

Uptime

99.97%

Rolling 30-day · commitment 99.95%

Drift

Events diverged · zero tolerance

Latency p95

1.42s

Order intake → reconcile ack

Error Rate

0.04%

Rolling 24-hour · manual: 12%

The SLOs

Four objectives. Measured continuously.

The layer commits to four service-level objectives: availability, latency, reconciliation lag, and drift. Each is measured continuously and externally reportable. Click any row to see the current status and measurement methodology.

Availability 99.95% 99.97% ● Met

Latency p95 < 2.0s 1.42s ● Met

Reconciliation Lag < 60 min 47 min ● Met

Drift 0 0 ● Met

The Contrast

Ad-hoc integration.
Or standard surface.

Ad-hoc integration means custom bridges, bespoke endpoints, and unrepeatable patterns. Standard surface means documented interfaces, published contracts, and repeatable deployment. The layer uses the standard surface.

Ad-hoc Integration

Custom Path

Custom SAP exits and proprietary bridges
Unrepeatable per implementation
Documentation drifts from reality
Vendor-locked — hard to replace
No end-to-end tracing
Upgrades break at unknown points

Standard Surface

Open Path

Standard SAP interfaces only
Repeatable across deployments
Open contracts documented and versioned
Vendor-neutral — interfaces are standard
Full OpenTelemetry tracing
SAP upgrades are standard change management

Questions

Integration, answered.

Three surfaces. SAP-native: OData for reads, BAPI for transactional writes, RFC for scheduled jobs, IDoc for asynchronous events. Layer-native: REST for direct calls, server-sent events for real-time streams, webhooks for event-driven workflows. Observability: OpenTelemetry metrics, traces, and logs, plus health check endpoints and a public status page.

Full observability via OpenTelemetry-compatible metrics, traces, and logs. The reconciliation drift meter is one of the standard observability signals. Everything is traceable end-to-end — the same trace ID follows an order from intake through reconciliation ack. No proprietary dashboards required.

Standard retry policies with exponential backoff. Idempotency keys prevent double-writes — critical for reliable SAP integration. Dead-letter queues preserve failed events for manual replay without data loss. Every error is logged with full context including trace ID, request ID, and the specific failure reason.

99.95% uptime commitment. Multi-region failover. Health check endpoints published for external monitoring. Status page available to operational teams. Current rolling 30-day uptime: 99.97%.

Yes. The integration surface uses standard interfaces and open contracts. Additional endpoints can be exposed as operational requirements emerge. No proprietary protocols required. No vendor lock-in. The contract definition is the extension point — add an endpoint, document it, publish it. Standard change management.

Standard interfaces. Full observability. End-to-end traceability.

Three tiers. Fifteen endpoints.Every one a standard interface.

/sap/odata/v4/Orders({id})

Watch an order flow through five hops.

Four live signals. Continuous.

Four objectives. Measured continuously.

Ad-hoc integration.Or standard surface.

Ad-hoc Integration

Standard Surface

Integration, answered.

What integration surfaces does the layer expose?

How is observability handled?

How are errors and retries handled?

What is the layer's uptime commitment?

Can the integration surface be extended?

Standard surface. Standard interfaces.

Standard interfaces.
Full observability. End-to-end traceability.

Three tiers. Fifteen endpoints.
Every one a standard interface.

Ad-hoc integration.
Or standard surface.