Everything in CAP
Type
Domain
Origin: Community org
Signals: 2
More
Group by: Capability
Six CAP features in one package, from replication cache to rate limits
It is a bundle, not a plugin with one job. Depending on it for one feature brings the rest.
Exposes a CAP service as OData V2
WebSocket and Socket.IO adapter for CDS services
Six CAP features in one package, from replication cache to rate limits
It is a bundle, not a plugin with one job. Depending on it for one feature brings the rest.
Six CAP features in one package, from replication cache to rate limits
It is a bundle, not a plugin with one job. Depending on it for one feature brings the rest.
Spreadsheet upload into a CDS entity, parsed on the server
Six CAP features in one package, from replication cache to rate limits
It is a bundle, not a plugin with one job. Depending on it for one feature brings the rest.
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.
SDK for SAP Advanced Financial Closing scheduling providers on CDS
Six CAP features in one package, from replication cache to rate limits
It is a bundle, not a plugin with one job. Depending on it for one feature brings the rest.
Live-updatable feature toggles for CAP, backed by Redis
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.
CLI for operating tenants of multitenant CAP applications
Business-level metrics from CDS annotations via @cap-js/telemetry
Six CAP features in one package, from replication cache to rate limits
It is a bundle, not a plugin with one job. Depending on it for one feature brings the rest.
Dev-time wrapper for the SAP Application Router
Showcase for dev-approuter in front of two UI5 apps
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.
CAP bookshop showing UI5 development with cds-plugin-ui5
Versioned specification of the abap2UI5 roundtrip protocol
Neither suite has been run against an ABAP system: the reference backends are the framework transpiled to Node and cap2UI5 on CAP, so what a check does on a real system is open. The portable profile is a subset of 61 controls, filled from a census of 247 core apps of which 64.8 % run unchanged, so an app outside it renders placeholders in the terminal and Adaptive Cards renderers.
UI5 app consuming the cds-bookshop server via ui5-middleware-cap