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.

Where it sits

Lives in
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

What it declares

Every artifact

Type
Service
Origin
By SAP

As a service

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

Connections3

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