Everything in CAP
Type: CDS plugin
Domain
Origin: Community org
Signals
More
Group by: Capability
Distributed through
Exposes a CAP service as OData V2
WebSocket and Socket.IO adapter for CDS services
Spreadsheet upload into a CDS entity, parsed on the server
Transactional processing of asynchronous and periodic CAP events
If you need sub-second fan-out to external consumers this is the wrong layer — reach for [Event Mesh](artifact:btp-event-mesh) or Kafka. Without [Redis](external:redis), periodic processing still works but instant dispatch degrades to polling.
Transactional processing of asynchronous and periodic CAP events
If you need sub-second fan-out to external consumers this is the wrong layer — reach for [Event Mesh](artifact:btp-event-mesh) or Kafka. Without [Redis](external:redis), periodic processing still works but instant dispatch degrades to polling.
Business-level metrics from CDS annotations via @cap-js/telemetry
Gherkin scenarios driving a running CAP service
UI5 CLI middlewares running inside the CDS server
For a deployed application's UI. The README adds it with `npm add cds-plugin-ui5 -D`, a development dependency of the CDS server, and states nothing about a build or a deployment.