![](https://community.sap.com/html/assets/img_tile-default.png)
In July 2019, we witnessed an evolution of the SAP BTP strategy with a strong focus on building differentiating business service capabilities and clear intentions to partner with hyperscale cloud providers like Amazon, Microsoft, AliCloud and GCP for commodity technical services like open-source databases and data stores; where these hyperscalers are already market leaders.
In February 2020, considering customer/partner feedback about challenges with the BYOA (Bring Your Own Account) approach, we announced an update to the backing service strategy, with plans to deliver a comprehensively managed backing services offering:
For more details please check SAP BTP Discovery Center and the service documentation on SAP Help Portal.
Redis on SAP BTP, hyperscaler option is globally available via CPEA and PAYG commercial models, for China is available via subscription commercial model. Now, Redis on SAP BTP, hyperscaler option is available for customers on BTP@China!
You need to have a Global Account with the proper entitlements to be able to use Redis service.
The number of units of a particular plan/SKU that get consumed when you provision a redis-cache instance depends on the chosen plan and the technical configuration.
The number of SKU units also differ across infrastructure regions, because of the differences in the Redis service offered by the underlying infrastructure provider.
You can choose to use Standard plan (instances based on 2GB memory increase) and Premium Plan (instances based on 4GB memory blocks).
For China you can refer to Help Portal service documentation: Service Plans and Entitlements AliCloud instance configuration options.
After making sure that you have sufficient entitlements quota assigned for your instance, then you can create an instance with CLI. Alternatively, you can create via SAP BTP Cockpit.
cf marketplace -e redis-cache
cf create-service SERVICE PLAN SERVICE_INSTANCE [-c PARAMETERS_AS_JSON]
For example:
cf create-service redis-cache standard redis-cache-instance -c
'{
"memory": 2,
"engine_version": "4.0",
"eviction_policy": "noeviction",
"shard_count": 1,
"node_count": 2
}'
Notes for AliCloud region:
- Engine version 6.0 not supported.
- The shard_count can be updated, however it is not allowed to update it from 1 (non-clustered) to 2 or more (clustered instance).
- Only Redis instances with a shard count of >1 support TLS connections.
cf service <service-instance-name> --guid //Note the service instance id
cf curl /v2/service_instances/<service-instance-id>/parameters
Sample output:
{
"engine_version": "4.0",
"eviction_policy": "noeviction",
"memory": 2,
"node_count": 1,
"shard_count": 2
}
cf enable-ssh <app-name>
cf restart <app-name>
cf create-service-key <instance-name> <key-name>
cf service-key <instance-name> <key-name>
cf ssh -L 6666:<hostname>:<port> <app-name>
redis-cli [--tls] -c -p 6666 -a <instance-password>
For more details: Access a Redis-cache Instance from Redis-cli
You can do it in the same way as the BYOA (Bring Your Own Account) approach. You can consume the Redis instance via app binding and the app runtime environment variable.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
34 | |
13 | |
11 | |
11 | |
10 | |
9 | |
9 | |
9 | |
8 | |
7 |