Multi-region active-active (in development).
Active-active means accepting writes in more than one region. This mode is in development and is not available for customer provisioning. The sections below describe the goal, not a released service or a delivery date.
- Write down recovery needsDefine acceptable downtime, data loss and required regions.
- Review available configurationsConsider the currently supported primary and standby options.
- Confirm recovery behaviorCheck replication lag, failover steps and deployment limits.
- Test the supported setupValidate recovery before depending on it in production.
What it is designed to do.
The intended design lets clients write in different regions while the engines agree on committed data. That requires replication and recovery rules for every supported write operation, including indexes and schema changes. Those guarantees are not established by this guide.
For a current deployment, plan around its actual primary/standby configuration and documented recovery procedure.
When to choose it.
Consider this requirement when users in several regions must write locally. First identify which operations need that behavior, how much delay is acceptable and what data loss the application can tolerate.
If one write region is enough, evaluate a supported regional configuration instead of depending on an unreleased mode.
Getting set up.
There is no customer setup procedure or release date for this mode. Contact the team with your regions, write workload and recovery requirements. Do not make a production commitment until the offered configuration and its guarantees are confirmed.