Login DE | EN | FR | PT
← Back to overview
13 August 2024

Maintenance measure to improve the database infrastructure

The database infrastructure has been improved. Previously, the database ran in single-AZ mode (= availability zone). As a result of the changeover, the database was converted into a multi-AZ mode.

The changeover means that the database is converted from a configuration in which it is only operated in a single availability zone to a configuration in which it is operated simultaneously in several availability zones within a region.

What does this mean?

  • Single AZ mode: The database runs in a single availability zone. If this zone fails or other problems occur, this can affect the accessibility of the database, which can lead to downtime or data loss.
  • Multi-AZ mode: Here the database is operated in multiple availability zones. The primary instance of the database runs in one AZ, while a secondary, synchronised replication is provided in another AZ. This replication is continuous and synchronised so that both instances have the same data at all times.

Advantages of switching to multi-AZ mode

  1. Higher availability: By using multiple availability zones, the database becomes highly available. If the primary instance fails, the service can automatically switch to the secondary instance, minimising downtime.
  2. Automatic failover: In the event of a failure of the primary instance, whether due to hardware failure, network failure or scheduled maintenance, a failover to the secondary instance is automatically performed. This takeover is transparent for the application and the end user.
  3. Data consistency and integrity: Synchronous replication between the AZs ensures that no data is lost, even if a complete failure of one AZ occurs. All write operations are performed simultaneously in both instances, ensuring that the data always remains consistent.
  4. Scalability and performance optimisation: The multi-AZ mode makes it possible to better distribute loads and optimise performance. For read-heavy applications, for example, additional read replicas can be created in other AZs to improve read access.
  5. Increased security: Spatial separation of instances across different AZs increases the security of the database, as potential threats or attacks affecting a single AZ do not jeopardise the entire database.

Switching a database from single-AZ mode to multi-AZ mode is an important measure for increasing the availability, reliability and security of the database infrastructure. It ensures that the database can continue to operate even in the event of failures in an AZ, which is essential for critical applications. The advantages in terms of automatic failover, data stability and scalability make multi-AZ mode a recommended configuration for applications with high reliability requirements.


This measure is made possible by the many loyal users who have purchased a licence in recent weeks. Thank you very much for your support. We are also working on new features and are looking forward to releasing them.


» Older entry: monkkee goes pro