Current Limitation
When the APIM 4.1.0 server is configured to use a read-only database, it fails to complete startup.
Suggested Improvement
Since the deployment pattern is already valid from a database perspective, it would be beneficial for the APIM to support operating with a read-only database and function purely as a hot disaster recovery (DR) node.
In this mode, the APIM should remain passive and not serve traffic while the databases are in read-only state. Traffic serving should begin only after write access to the databases is explicitly enabled.
Additionally, APIM should not automatically detect or react to changes in database write access. Instead, the transition from passive (DR) to active mode should be controlled through an explicit administrative action, ensuring better predictability and operational control.
Version
No response
Current Limitation
When the APIM 4.1.0 server is configured to use a read-only database, it fails to complete startup.
Suggested Improvement
Since the deployment pattern is already valid from a database perspective, it would be beneficial for the APIM to support operating with a read-only database and function purely as a hot disaster recovery (DR) node.
In this mode, the APIM should remain passive and not serve traffic while the databases are in read-only state. Traffic serving should begin only after write access to the databases is explicitly enabled.
Additionally, APIM should not automatically detect or react to changes in database write access. Instead, the transition from passive (DR) to active mode should be controlled through an explicit administrative action, ensuring better predictability and operational control.
Version
No response