Available Persistence Options with Aptible Managed Redis Instances

When provisioning Redis instances on Aptible, you can choose between different persistence options depending on your application needs.

Key considerations:

• Is Redis only being used as a cache, or is persistence required?

• If persistence is important, is RDB + AOF required (the current default image type)?

Persistence methods:

• RDB (Redis Database Backups): Periodic snapshots of the dataset. Minimal data loss risk between snapshots.

• AOF (Append Only File): Logs every write operation. Enables recovery even after crashes with minimal data loss.

• By default, we combine both RDB and AOF to balance persistence and performance.

If persistence is not required:
You can create a Redis instance without persistence, meaning the database only uses in-memory storage. If the instance restarts, all data will be lost and must be recreated.

Example command to create a no-persistence Redis database:

aptible db:create HANDLE --type redis --version 7.0-nordb [--container-size SIZE_MB] [--disk-size SIZE_GB]

Available Redis 7 versions:

• 7.0: RDB-only persistence

• 7.0-aof: RDB + AOF persistence (default)

• 7.0-nordb: No persistence

Disk sizing recommendations:

• If using RDB + AOF: Allocate disk space equal to at least 4x the container memory size to accommodate RDB snapshots and AOF rewrite operations.

• If using RDB only: Allocate disk space equal to at least 2x the container memory size.

• If using no persistence: A minimal 10 GB disk volume is sufficient.

Please contact Aptible Support if you have any questions or need additional assistance.