Redis
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.
Where it sits
Used by
Dependency relationship. Carries events between application instances over publish/subscribe — the part that makes the queue load-balanced across a scaled app rather than per instance.
Functional boundary
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.
Dependency relationship.
Optionally used: a high availability setup; the requirement is marked Optional; Required for HA the data store an Edge Integration Cell uses at 6.x or 7.x, with access key authentication and at least 1 CPU and 1 GiB
Optionally used: When store: "redis" is selected. Cache storage through @keyv/redis; other store modes do not require this backend.
Functional boundary
When user-dependent responses are cached without user-aware or explicit operation keys, or translated responses share keys across locales. These cases require key isolation; locale-aware keys are off by default.
Optionally used: A messaging service is configured with kind redis-pubsub.
Connected from
data. passing cache read and write operations through to the Redis store at runtime
Functional boundary
When user-dependent responses are cached without user-aware or explicit operation keys, or translated responses share keys across locales. These cases require key isolation; locale-aware keys are off by default.
On BTP
A managed 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. from the underlying hyperscaler, consumed through a BTP service binding rather than run yourself.