You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Choreo-Managed Cache is a fully-managed Valkey™ offering, an in-memory NoSQL database service that offers high performance, scalability, and security.
4
4
5
-
Choreo-Managed Cache provides fully-managed in-memory NoSQL databases on AWS, Azure, GCP, and Digital Ocean and can be used as a cache, database, streaming engine, or message broker.
5
+
Developed under the Linux Foundation, Valkey™ is an open-source fork of Redis® designed to provide a seamless and reliable alternative to Redis OSS. Choreo-Managed Caches with Valkey™ ensures full compatibility with Redis OSS v7.2.4.
6
6
7
7
## Create a Choreo-Managed Cache
8
8
@@ -25,20 +25,22 @@ Follow the steps below to create a Choreo-Managed Cache:
25
25
26
26
To connect to your Choreo-Managed Cache, follow these guidelines:
27
27
28
-
- Use any legacy Redis® OSS compatible driver (in any programming language) to connect to your Choreo-Managed Cache.
28
+
- Use any Redis® OSS compatible driver (in any programming language) to connect to your Choreo-Managed Cache.
29
29
- You can find the connection parameters in the **Overview** section in the Choreo Console under the relevant database. Note that Choreo-Managed Cache enforces TLS.
30
30
- Choreo-Managed Cache instances accept traffic from the internet by default. You can restrict access to specific IP addresses and CIDR blocks under **Advanced Settings**.
31
31
32
32
## High availability and automatic backups
33
33
34
34
The high availability and the automatic backup retention periods for a Choreo-Managed Cache can vary as follows depending on the service plan you select.
35
35
36
-
| Service plan | High availability | Backup features | Backup history |
| Hobbyist | Single-node with limited availability. | Single backup only for disaster recovery | None | No |
39
+
| Startup | Single-node with limited availability. | Single backup only for disaster recovery | 1 day | No |
40
+
| Business | Two-node (primary + standby) with higher availability (automatic failover if the primary node fails). | Automatic backups | 3 days | Yes*|
41
+
| Premium | Three-node (primary + standby + standby) with highest availability (automatic failover if the primary node fails). | Automatic backups | 13 days | Yes*|
42
+
43
+
*Multi‑AZ availability depends on the cloud provider and region and is enabled where supported.
42
44
43
45
In general, service plans are recommended for production scenarios due to the following reasons:
44
46
@@ -48,9 +50,10 @@ In general, service plans are recommended for production scenarios due to the fo
48
50
49
51
### Automatic backups
50
52
51
-
- Choreo runs full backups daily to automatically backup Choreo-Managed Caches and has write-ahead logs (WAL) copied at 5-minute intervals or for every new file generated.
52
-
- Choreo encrypts all backups at rest.
53
-
- Choreo automatically handles outages and software failures by replacing broken nodes with new ones that resume correctly from the point of failure. The impact of a failure will depend on the number of available standby nodes in the data store.
53
+
- Automated snapshots and append‑only logging (where applicable) are used to support recovery
54
+
- Backups are encrypted at rest
55
+
- Backups are managed automatically during recovery; manual backup point selection is not supported
56
+
- Choreo automatically handles outages and software failures by replacing broken nodes with new ones that resume correctly from the point of failure. The impact of a failure will depend on the number of available standby nodes in the data store
Copy file name to clipboardExpand all lines: en/developer-docs/docs/manage-databases-and-caches/choreo-managed-databases-and-caches.md
+54-3Lines changed: 54 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,15 +1,44 @@
1
1
# Choreo-Managed Databases, Vector Databases, and Caches
2
2
3
-
Choreo allows you to create PostgreSQL and MySQL databases as well as Choreo-Managed Cache instances on all major cloud providers (AWS, Azure, GCP, and DigitalOcean) as fully Choreo-managed platform services.
3
+
Choreo allows you to create PostgreSQL and MySQL databases as well as Choreo-Managed Cache instances (Valkey) on all major cloud providers (AWS, Azure, GCP, and DigitalOcean) as fully Choreo-managed platform services.
4
4
These databases and caches can be seamlessly provisioned to offer persistence and caching capabilities for all your Choreo components. Choreo provides various service plans for each type, ranging from smaller instances for development purposes to production-grade databases with automatic backups and high-availability multi-nodes.
5
5
6
+
## Technology Partnership
7
+
8
+
Choreo's managed data services are powered by **Aiven.io**, our trusted technology partner and data platform subprocessor. Aiven provides the underlying infrastructure, automated management, and expertise that enable Choreo to deliver fully managed data services as part of our ecosystem.
9
+
10
+
### Service Level Agreement (SLA)
11
+
12
+
Choreo-managed data services inherit Aiven's 99.99% monthly uptime SLA. For detailed terms, see Aiven's Service Level Agreement (https://aiven.io/sla).
13
+
14
+
### Security and Compliance
15
+
16
+
Choreo benefits from Aiven's security program and industry-standard certifications. For the latest list of certifications and protections, see Aiven Security, Privacy & Compliance (https://aiven.io/security-compliance). Typical controls include encryption in transit and at rest, dedicated VMs, and automated security updates.
17
+
6
18
!!! info "Note"
7
19
- The capability to create Choreo-managed databases, vector databases, and cache services is available only for paid Choreo users.
8
20
- Billing for these services will be included in your Choreo subscription, with pricing varying based on the service plan of the resources you create. For more details, see [Choreo Platform Services Billing](../references/choreo-platform-services-billing-and-upgrades.md#platform-service-billing-information).
9
21
10
22
!!!Tip "Explore the free trial"
11
23
Choreo provides a 7-day free trial for all database types on the 'Hobbyist' service plan, available to free-tier users.
12
24
25
+
## Support Model
26
+
27
+
Choreo provides support for managed data services directly and, when needed, in coordination with Aiven:
28
+
29
+
- Guidance and operational assistance via Choreo support
30
+
- Coordination with Aiven experts for complex technical issues
31
+
- Choreo acts as your primary contact and manages escalations with the Aiven support team as required
32
+
33
+
## Service Limitations and Considerations
34
+
35
+
### Backup Management
36
+
All managed data services include automated, encrypted backups. Manual backup point selection is not supported; services automatically restore from the most recent available backup during recovery.
37
+
38
+
### Monitoring and Observability
39
+
- Runtime metrics (CPU, memory, disk, network) and service/database logs are available in the Choreo Console
40
+
- Native alerting for resource spikes is not currently available; contact Choreo support if you need to export metrics to third‑party monitoring
41
+
13
42
## PostgreSQL on Choreo
14
43
15
44
PostgreSQL (also known as Postgres), is an open-source object-relational database management system. You can create PostgreSQL databases on Choreo as fully Choreo-managed, flexible SQL databases that are ideal for both structured and unstructured data. If you want to perform an efficient vector similarity search, you can create a PostgreSQL vector database.
@@ -22,12 +51,34 @@ MySQL is a user-friendly, flexible, open-source relational database management s
22
51
23
52
-[Create a MySQL database on Choreo](./choreo-managed-mysql-databases.md)
24
53
25
-
## Choreo-Managed Cache
54
+
## Choreo-Managed Cache (Valkey Compatible)
26
55
27
-
A fully-managed cache compatible with legacy Redis® OSS. A versatile, in-memory NoSQL database that serves as a cache, database, streaming engine, and message broker. Choreo-managed Cache allows you to have fully-managed instances that can be swiftly provisioned and integrated into your applications within minutes.
56
+
A fullymanaged cache compatible with Redis® OSS and Valkey. A versatile, in‑memory NoSQL database that serves as a cache, database, streaming engine, and message broker. Choreo-managed Cache allows you to have fullymanaged instances that can be swiftly provisioned and integrated into your applications within minutes.
28
57
29
58
-[Create a Choreo-managed Cache](./choreo-managed-caches.md)
30
59
60
+
## Is a Choreo-Managed Database Right for You?
61
+
62
+
Use this checklist to evaluate fit:
63
+
64
+
### Good fit
65
+
- Need fully managed data infrastructure with minimal ops overhead
66
+
- Expect high availability with automated failover (99.99% SLA)
67
+
- Need strong security practices and industry certifications
68
+
- Prefer automatic encrypted backups and managed recovery flows
69
+
70
+
### Consider alternatives if you
71
+
- Require manual backup point selection and granular point‑in‑time control
72
+
- Need native alerting and advanced monitoring immediately
73
+
- Have region/compliance constraints not currently available
- Validate backup/recovery and monitoring for your use case
80
+
- Use Business or Premium in production for higher availability
81
+
31
82
<spanstyle="font-size: 11px; color:gray;">
32
83
PostgreSQL, MySQL, and Redis® are trademarks and property of their respective owners. All product and service names used in this documentation are for identification purposes only.
Copy file name to clipboardExpand all lines: en/developer-docs/docs/manage-databases-and-caches/choreo-managed-mysql-databases.md
+28-8Lines changed: 28 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,8 @@
2
2
3
3
MySQL on Choreo offers fully managed, flexible relational databases on AWS, Azure, GCP, and Digital Ocean.
4
4
5
+
These services run on infrastructure and automation provided by [Aiven](https://aiven.io), our technology partner and data platform subprocessor. For details on the partnership, SLA, and security posture, see the overview (./choreo-managed-databases-and-caches.md#technology-partnership).
6
+
5
7
## Create a Choreo-managed MySQL database
6
8
7
9
Follow the steps below to create a Choreo-managed MySQL database:
@@ -29,12 +31,14 @@ To connect to your Choreo-managed MySQL database, consider the following guideli
29
31
30
32
The high availability characteristics and the automatic backup retention periods for Choreo-managed MySQL databases vary based on your service plan as explained below:
31
33
32
-
| Service Plan | High Availability | Backup Retention Time |
| Hobbyist | Single-node with limited availability | None | No |
37
+
| Startup | Single-node with limited availability | 2 days | No |
38
+
| Business | Two-node (primary + standby) with higher availability | 14 days | Yes*|
39
+
| Premium | Three-node (primary + standby + standby) with highest availability | 30 days | Yes*|
40
+
41
+
*Multi‑AZ availability depends on the cloud provider and region and is enabled where supported.
38
42
39
43
In general, we recommend service plans for production scenarios for multiple reasons:
40
44
- Provides another physical copy of the data in case of hardware, software, or network failures.
@@ -43,11 +47,27 @@ In general, we recommend service plans for production scenarios for multiple rea
43
47
44
48
### Automatic Backups
45
49
46
-
- Choreo runs full backups daily to automatically back up Choreo-managed MySQL databases and record binary logs continuously.
47
-
Choreo encrypts all backups at rest.
50
+
- Daily full backups of MySQL databases are taken automatically
51
+
- Logs are recorded to support point‑in‑time recovery where applicable
52
+
- All backups are encrypted at rest
53
+
- Backups are managed automatically during recovery; manual backup point selection is not supported
48
54
49
55
- Choreo automatically handles outages and software failures by replacing broken nodes with new ones that resume correctly from the point of failure. The impact of a failure will depend on the number of available standby nodes in the database.
50
56
57
+
### Failure Recovery
58
+
59
+
- Minor failures (e.g., process restarts or transient network issues) are handled automatically without requiring changes to the deployment
60
+
- For severe failures (e.g., node loss), monitoring detects the issue and schedules a replacement node automatically
61
+
- In database failover scenarios, the Service URI remains the same; the IP address changes to point to the new primary node
62
+
- For single‑node tiers, the service is unavailable during restoration and some recent writes may not be recoverable
63
+
64
+
Typical outcomes in multi‑node tiers include automatic failover within minutes and recovery workflows designed to minimize data loss.
65
+
66
+
## Monitoring and Observability
67
+
68
+
- Runtime metrics (CPU, memory, disk, network) and MySQL logs are available in the Choreo Console
69
+
- Native alerting for resource spikes is not currently available; contact Choreo support if you need to export metrics to third‑party monitoring for custom alerting.
70
+
51
71
## Connection Limits
52
72
53
73
The maximum number of simultaneous connections to MySQL databases is fixed for each service plan and depends on how much RAM your service plan offers.
0 commit comments