Anna Pleshakova
Jan 27, 2025
visibility 2686
star star star star star
(0 votes)

Further Enhancing Production Database Scalability in DXP Cloud Services

About a year ago we announced that we are improving the scalability of SQL databases in DXP Cloud Services, focusing first on non-production databases. After seeing the benefits and carefully testing the impact in lower environments, we are now ready to extend this to production. 
 
To recap, the benefits of this new architecture are: 
  • Management efficiency – Our solution simplifies the operation of hundreds, even thousands, of databases. It ensures all databases receive the necessary resources, driving optimal performance across various workloads. 
  • Auto-scaling – The system can intuitively allocate more resources during high-demand periods, maintaining high efficiency and responsiveness under fluctuating loads. 
  • Enhanced access security for SQL databases – We hardened technical controls to maintain confidentiality and integrity of customer data. 
As mentioned in a previous blog post on this topic, this change has a consequence of disallowing developers having direct access to the database and its metrics. We are confident that the benefits mentioned above significantly outweigh this drawback.   
 
We are very eager to now extend the performance and scalability benefits across the platform’s production databases in 2025! Each customer will be contacted by our team at Optimizely to ensure we make this transition as seamlessly as possible. No immediate action is required from customers. 
 
Questions? Here are some common FAQs below:

Q: How will this affect our live instances during the upgrade?
A: During the migration there will be a short downtime, on average it’s 3-5 minutes but can take a little longer depending on implementation.

Q: Why do some databases take longer to migrate?
A: Transient issues in cloud infrastructure, high database load and/or slow application initialization. There are multiple reasons that can have an impact. The vast majority just takes 3-5 minutes. 

Q: Could any orders be lost during the migration window?
A: We recommend the maintenance page to prevent order loss. 

Q: What happens to changes made in the CMS during the maintenance period? 
A: Changes saved before the final step of the maintenance window will be saved.

Q: What happens to sessions and carts that are in the process of being converted into orders during checkout? 
A: Orders will be accepted up to the final step when the database is migrated. Once migrated, the web app will be started again. 

Jan 27, 2025

Comments

error Please login to comment.
Latest blogs
Composition Over Inheritance: Why Your Content Contract Is Not a Base Class

Inside the structural conformance pattern in SaaS CMS — from server-side inheritance to pipeline governance. A contract in Optimizely SaaS CMS is...

Vipin Banka | Sep 19, 2026

Optimizely Opti ID Integration: Why the API Key Was Missing from the DXP Management Portal

While working on an Optimizely CMS 12 Opti ID integration recently, we ran into an issue that initially appeared to be related to SSO authenticatio...

Madhu | Sep 18, 2026 |

Extending a Contract: What You Can Override

Contracts share fields across content types — but not every field setting can be overridden. Push the same contract onto several components, and CM...

Chirag Khanna | Sep 18, 2026 |

Building a Blazor Server UI Inside the Optimizely CMS 13 Admin Shell

What I learned shipping a Blazor Server UI inside Optimizely CMS 13 — Razor components in a NuGet package, the Blazor hub next to MapContent(),...

Stanisław Szołkowski | Sep 17, 2026 |