PackagePackageA library you install and call yourself.See every one →What this type is →by SAPby SAPPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →
com.sap.cds:cds-feature-redis
A beta CAP Java feature that connects a CAP messaging service to Redis Pub/Sub, which broadcasts each event to every subscribed instance and does not guarantee delivery.
Connects a CAP messaging service to RedisRedisAn in-memory data store. For the things here it is the shared cache, the queue or the pub/sub channel that lets several application instances behave as one. Pub/Sub, one of the optional application features that build on the CAP Java runtimecom.sap.cds:cds-services-bomThe Maven bill of materials for CAP Java, pinning every com.sap.cds module in a release, from the API and core runtime to the Spring Boot starters and the CQN engine, to the same version.sap official, cap, and is itself a beta feature. It ships as a Maven dependency and activates when a messaging service is configured with kind redis-pubsub. Unlike SAP Event MeshEvent MeshManaged queues and topics over AMQP, MQTT and a REST gateway, and the bus SAP's own applications publish their business events to.sap official, btp, Redis events are broadcast to every subscribed client at once, so each application instance receives the same event, and delivery is not guaranteed: an instance that is not connected to the Redis service when an event is sent never receives it.
Facts
LicenceSAP DEVELOPER LICENSE AGREEMENT for CAP
Where it sits
Lives in
Provides
Event MeshCAPEvent MeshEmitting and consuming business events across systems through brokers, including subscriptions and mapping application events to broker topics. Work that must survive a request, including deferred processing and retries, belongs to [async processing](capability:async-processing).
Flavors
Optional
RedisRedisA messaging service is configured with kind redis-pubsub.message broker
What it declares
Every artifact
- Type
- Package
- Origin
- By SAP
- Runtime
- Java
As a package
- Where it runs
- does not say
- Distributed through
- does not say
Connections
Group by
NodeRelationBasis
Functional
Event MeshEvent MeshEmitting and consuming business events across systems through brokersSAP and community, narrow by design
provides
stated
provides Event Mesh
Connects a CAP messaging service to [Redis](external:redis) Pub/Sub as a beta broker, where every subscribed application instance receives the same broadcast event and delivery is not guaranteed.
“the Redis feature is a PubSub service which means that the Redis events are broadcasted and delivered to all subscribed clients simultaneously”“it's not guaranteed that really all events are delivered by the infrastructure”
Emitting and consuming business events across systems through brokers
Technical
Redis on SAP BTP, hyperscaler optionRedis on SAP BTP, hyperscaler optionManaged Redis from the hyperscaler via a BTP service bindingsap official, btp
available via
derived
available via Redis on SAP BTP, hyperscaler option
Managed Redis from the hyperscaler via a BTP service binding
optionally needs
stated
optionally needs Redis
A messaging service is configured with kind redis-pubsub.
“the Redis feature is a PubSub service which means that the Redis events are broadcasted and delivered to all subscribed clients simultaneously”
An in-memory data store. For the things here it is the shared cache, the queue or the pub/sub channel that lets several application instances behave as one.
Download
Where it sits in your app
Download
RedisAn in-memory data store. For the things here it is the shared cache, the queue or the pub/sub channel that lets several application instances behave as one.
com.sap.cds:cds-feature-redisA beta CAP Java feature that connects a CAP messaging service to Redis Pub/Sub, which broadcasts each event to every subscribed instance and does not guarantee delivery.sap official, cap
com.sap.cds:cds-feature-redis → RedisDocumented only, under a conditionIf A messaging service is configured with kind redis-pubsub.
SAPnot SAP's, or the project's ownunder a condition
Others providing
Compare all 14 on the Event Mesh page →Event MeshEvent MeshEmitting and consuming business events across systems through brokers, including subscriptions and mapping application events to broker topics. Work that must survive a request, including deferred processing and retries, belongs to async processing.SAP and community, narrow by design
- SAP Integration Suite, advanced event meshSAP Integration Suite, advanced event meshAn event streaming, event management and monitoring platform for event-driven architecture, offered within SAP Integration Suite.sap official, btpEvent streaming and management platform in Integration Suite
- Event MeshEvent MeshManaged queues and topics over AMQP, MQTT and a REST gateway, and the bus SAP's own applications publish their business events to.sap official, btpManaged queues and topics over AMQP, MQTT and REST
- com.sap.cds:cds-feature-advanced-event-meshcom.sap.cds:cds-feature-advanced-event-meshA beta CAP Java plugin that adds SAP Integration Suite, advanced event mesh as a messaging broker, activated by setting a messaging service's kind to aem.sap official, capCAP Java plugin for SAP Integration Suite, advanced event mesh
- com.sap.cds:cds-feature-enterprise-messagingcom.sap.cds:cds-feature-enterprise-messagingA CAP Java feature that connects a CAP messaging service to SAP Event Mesh, activated by setting the service's kind to enterprise-messaging, and looks up the bound instance.sap official, capConnects CAP Java messaging to SAP Event Mesh
- com.sap.cds:cds-feature-event-hubcom.sap.cds:cds-feature-event-hubA CAP Java plugin that connects CAP's messaging service to SAP Cloud Application Event Hub, so an application sends and consumes business events without coding against its API.sap official, capConnects CAP Java messaging to SAP Cloud Application Event Hub
- com.sap.cds:cds-feature-kafkacom.sap.cds:cds-feature-kafkaA CAP Java feature that connects a CAP messaging service to Apache Kafka for intra-application messaging, through the Apache Kafka client library rather than a managed SAP messaging service.sap official, capConnects CAP Java messaging to Apache Kafka
- com.sap.cds:cds-services-bomcom.sap.cds:cds-services-bomThe Maven bill of materials for CAP Java, pinning every com.sap.cds module in a release, from the API and core runtime to the Spring Boot starters and the CQN engine, to the same version.sap official, capMaven bill of materials pinning CAP Java module versions
- @cap-js/advanced-event-mesh@cap-js/advanced-event-meshIntegrates CAP with SAP Integration Suite advanced event mesh.sap official, capCAP integration with SAP Integration Suite advanced event mesh
- @cap-js/asyncapi@cap-js/asyncapiExports AsyncAPI documents describing the events a CAP service emits and consumes.sap official, capExports AsyncAPI documents for a CAP service's events
- @cap-js/event-broker@cap-js/event-brokerConsumes events from SAP Cloud Application Event Hub.sap official, capConsumes events from SAP Cloud Application Event Hub in CAP
- cds-kafkacds-kafkaA Kafka adapter for CAP that registers Kafka topics as a CDS messaging service over KafkaJS, so emit and on work unchanged, with per-message keys, partitions and topics set through headers.independent, capKafka adapter exposing topics as a CDS messaging service
- cds-event-monitoringcds-event-monitoringA CAP plugin that stores every event received on its configured messaging topics in a table, with a Fiori-annotated service to browse them, resend events and drain a dead-message queue.independent, capStores, browses and resends messages a CAP service receives
- @sap/cds@sap/cdsThe CAP Node.js runtime, which compiles the CDS model, serves the services declared in it, answers generic requests before any handler runs, and loads every cds-plugin.sap official, capCAP Node.js runtime
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
runtimesjava
discovered viaAdded by hand
first seen in the atlas
ecosystem and domaincap, integration-and-messaging
Flavors
Java
“Redis feature for CDS Services Java” — com.sap.cds:cds-feature-redis — POM (5.1.1)
History in the atlas
- Connects a CAP messaging service to Redis Pub/Sub as a beta broker, where every subscribed application instance receives the same broadcast event and delivery is not guaranteed.
- First seen.
For your agent
- Ref
artifact:cap-java-cds-feature-redis- JSON
- /artifacts/cap-java-cds-feature-redis.json
- MCP
- Connecting an agent