Redis by VSHN

Redis, managed by VSHN for you.

The open source, in-memory data store used by millions of developers as a database, cache, streaming engine, and message broker.

— Redis Website
The user documentation is available under docs.appcat.ch.
Availability of the service

Features

Available sizing

1, 2 or 3 replicas

No downtime during Maintenance

[1]

Default user with unrestricted access

Maximum supported size of database

Size of selected memory

Persistence

[2]

Data encryption at rest

[3]

Guaranteed performance

[3]

High availability

[1]

Support

(see Support Plans)

The following common features are available as well:

Self-Service Instance Provisioning and Configuration

Service instances can be self-service ordered and are provisioned fully automated in the background. Access to self-service provisioning is provided via custom Kubernetes configuration objects in the Kubernetes cluster or via Open Service Broker API (on request).

Best-Practice Configuration Management

Services are configured with best practices and the configuration is updated continuously as we learn improvements during day-2 operations and from the community. Industry standards are used for security configuration and wherever possible TLS encrypted connections are offered by default.

Maintenance and Security Operations

Patch updates are applied as they get available. We monitor security information for services and apply zero-day patches or workaround configuration as they become available.

Data Protection and Recovery

All services offer a regular backup option. See the service descriptions for more details.

Service Metrics

Performance metrics are collected regularly and are available as graphs to the user. The metrics are automatically monitored and acted upon irregularities, see Monitoring and Alerting below.

Monitoring and Alerting

Service Level Indicators are monitored and alerted upon. Depending on the service level alerts are automatically handled by a VSHNeer.

Service Logging

All logs are collected and are available to debug service errors.

Support by VSHN or Vendor

Support for all services are available from VSHN support engineers. Depending on the service, additional support by the software vendor or a third-party might be available.

Supported versions

Supported versions:

  • Redis 8.0

  • Redis 7.2

  • Redis 7.0

Once a version isn’t supported anymore by the upstream project, we’ll stop supporting the version as well.

Upgrade Policy

Minor and major updates are done manually by the service user. Meanwhile, patch upgrades are done automatically during maintenance. The following upgrade policy support applies:

  • We continuously add new supported versions from the upstream project.

  • We only support a version as long as it’s supported upstream.

  • 3 months before the support ends ("Final Release") the grace period starts, and you’re urged to upgrade to a supported version.

  • Once the support for a service has ended, the service is considered "unmanaged" by VSHN. Meanwhile, the service still continues to run.

An unmanaged service is a service that is not monitored and SLA doesn’t apply anymore.

Service Level Indicator (SLI)

Redis responds to probes (Redis query) from within the same cluster. The service is considered up, if the query succeeds.

Please refer to Service Levels for further information about service levels. Also, check out "What does SLI / SLA / SLO mean?" for more information about these terms.

Incident Prevention

The capacity of the instances are monitored. If a threshold is reached an automated alert is generated to an alert channel of the customer’s choice.

  • The configured storage volume is in danger to run full

  • The memory is in danger to run low

Data Protection

Backups can be configured per instance.

By default, backups happen at a random time each day and 6 backups are kept. This schedule and the retention are configurable.

Backups are provided by K8up.

Recurring Maintenance

We conduct recurring maintenance tasks on the service to keep it stable and up-to-date.

Planned Maintenance Activities

  • Updating of the base container image with the latest patched version, this causes a service restart.

  • If there’s a newer minor version available that does not contain breaking changes, then the service will automatically be updated to that minor version.

  • Major upgrades are not automatic.

  • Configuration improvements as we learn new best-practices or some configuration proved to be non-optimal.

Mandatory Maintenance Activities

  • Security issue (CVE) mitigation by updating to a patched version or configuration adjustments, usually causes service restart.

  • Regular maintenance on the underlying platform, usually causing up to 2 restarts per replica.

Maintenance Windows

This is an automated recurrence once a week. The day and time can be configured per service instance, whereas by default it is a random time in the night from Tuesday to Wednesday.

Users responsibilities

As a DevOps company, we believe in its collaborative approach. Flawless service is only possible through a sense of responsibility on both sides. Accordingly, we rely on the user to consider the following points:

  • Choose reasonably sized resources for the software consuming the service

  • Act early when an increase in service usage is foreseen (for example increase resources)

  • Rely on best-practices for using the service

  • Choose a matching service level for your use-case

Behind the scenes

This service is provided by Bitnami package for Redis®. Service instances are running on the same Kubernetes cluster as the service instance was ordered in.

Pricing

Service Level Single Replicated (3 instances)

Best Effort

CHF 0.08333 / h

CHF 60.00 / 30d

CHF 0.24999 / h

CHF 180.00 / 30d

Guaranteed Availability

CHF 0.25 / h

CHF 180.00 / 30d

CHF 0.75 / h

CHF 540.00 / 30d

  • The computing resources required for the service are not included in the price and charged additionally.

  • "Replicated" are instances with a replication factor of 3.

  • For pricing, each additional replica counts as one additional instance.

  • Support is available at additional cost via Support Plans.

  • These prices are valid starting 2023-02-01 until further notice.

See Pricing for more details.

Service Maturity

This section describes the maturity of this service. We are constantly improving it and adding more features to the service.

Provisioning

✅

Backup

✅

Restore

✅

Logs

✅

Metrics

✅

Alerting

✅

Automated Maintenance

✅

Version Upgrades

✅

Scaling

❌

User Management

❌

FAQ

What do I need to get the service?

Currently the service is available on APPUiO and Managed OpenShift. Once you have access to such a cluster, it’s a matter of creating a Kubernetes object to order a service instance. In the getting started guide you’ll find all the information you need to get started.

Where do I get it?

As mentioned in the previous answer, the service is available on APPUiO and Managed OpenShift.

Are there any extra costs?

Yes, there are usage costs associated with the service. Please refer to VSHN AppCat Services Pricing for further information.

Who will set it up?

All services are available in full self-service. There is no need to open a ticket and wait until the service is provisioned, it’s available immediately.

What do I need to do?

The user documentation explains everything you need to know.

Can I get it myself or do I need to contact anyone?

There is no need to contact anyone, just follow the instructions on docs.appcat.ch and you’ll be up and running in no time.

How can it be integrated in my environment?

Services are available right now on APPUiO and Managed OpenShift. If you want these services on your environment, please contact us and we’ll help you get started.

How can I get support?

You can either open a ticket on our customer portal or send an email to support@vshn.ch. Please note that support is only available with our support plans.

1. With more than 1 replica
2. Persistence is enabled by default
3. Depends on the underlying platform