onedevatlasBeta
Browse the atlas
AllCAPBTPUI5ABAP
ServiceServicetypeA BTP service you subscribe to and bind, rather than install. It has plans and regions, not versions, and may deliver a product that lives outside the atlas.See every one →What this type is →by SAPby SAPoriginPublished 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 →

Redis on SAP BTP, hyperscaler option

A managed Redis from the underlying hyperscaler, consumed through a BTP service binding rather than run yourself.

Homepage
Docs

Where it sits

Lives in
BTP/BAIP
Provides
CachingBTPCAPCachingcapabilityHolding the result of an expensive read so the next one is cheap. This spans four different things people call caching — HTTP response caching, query result caching, remote service response caching, and application-level memoisation. They are not interchangeable, and picking the wrong one is the usual cause of stale-data bugs in multitenant apps.
Serves
CAP

What it declares

Every artifact

Type
Service
Origin
By SAP

As a service

Plans
5
Regions
46
Support component
BC-CP-BSB-REDIS

For caching

Caching layer
Redis cache service

Tasks this contributes to1Beta

Caching1
Share one cache across application instancesSeveral instances of the same application read and write one cache, so a result retained while serving one request answers a later request routed to a different instance.Node.jsCoversmanaged store
What it does

The instance an application binds when the redis store is configured. The plugin's deployment guide provisions service redis-cache in the mta descriptor and tags the instance cds-caching; SAP's service metadata records the plans the service offers, from a free plan for non-productive development to a premium one.

Remaining work

Provision an instance on a plan the subaccount is entitled to and bind it. Which plans a given subaccount may use is a project question, not a documented property of either the service or the plugin.

All options on the Caching page →

Connections3

Download
Redis on SAP BTP, hyperscaler option connectionsRedis on SAP BTP,hyperscaler optionPROVIDES→ delivers1delivers authoredRedis→ provides1provides stated Provides [Redis](external:redis) cache instances, with separate development and production-ready plans. SAP BTP service metadata — Redis: https://github.com/SAP-samples/btp-service-metadata/blob/main/v1/developer/redis-cache.jsonCachingUSED BY← used by1used by derived The approuter's external session store: the descriptor binds a redis-cache instance and names it as the store in the router's own configuration. Through: inverted from its requires edge miyasuta/cap-redis — mta.yaml: https://raw.githubusercontent.com/miyasuta/cap-redis/main/mta.yaml miyasuta/cap-redis — mta.yaml, resources: https://raw.githubusercontent.com/miyasuta/cap-redis/main/mta.yamlcap-redis

Others providing5

Compare all 6 on the Caching page →
Caching
  1. @cap-js-community/commonSix CAP features in one package, from replication cache to rate limitsfrom CAP
  2. cds-cachingCAP caching plugin for query results and remote service responsesfrom CAP
  3. ABAP-CACHE-BOXGenerates singleton ABAP cache classes from a macro callfrom ABAP
  4. cds-data-federationData federation for CAP via delegation, caching and replicationfrom CAP
  5. @sap/cdsCAP Node.js runtimefrom CAP

Details

Sources1
SAP-samples/btp-service-metadatadiscovered here, btp-service-metadatachecked

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
discovered viaSAP-samples/btp-service-metadata · btp-service-metadata
first seen in the atlas
ecosystem and domainbtp, data-and-persistence
History in the atlas1
  1. First seen.
For your agent
Ref
artifact:btp-redis
JSON
/artifacts/btp-redis.json
MCP
Connecting an agent