A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More

Anna Pleshakova
Jan 27, 2025
  2351
(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

Please login to comment.
Latest blogs
Looking back at Optimizely in 2025

Explore Optimizely's architectural shift in 2025, which removed coordination cost through a unified execution loop. Learn how agentic Opal AI and...

Andy Blyth | Dec 17, 2025 |

Cleaning Up Content Graph Webhooks in PaaS CMS: Scheduled Job

The Problem Bit of a niche issue, but we are building a headless solution where the presentation layer is hosted on Netlify, when in a regular...

Minesh Shah (Netcel) | Dec 17, 2025

A day in the life of an Optimizely OMVP - OptiGraphExtensions v2.0: Enhanced Search Control with Language Support and Synonym Slots

Supercharge your Optimizely Graph search experience with powerful new features for multilingual sites and fine-grained search tuning. As search...

Graham Carr | Dec 16, 2025

A day in the life of an Optimizely OMVP - Optimizely Opal: Specialized Agents, Workflows, and Tools Explained

The AI landscape in digital experience platforms has shifted dramatically. At Opticon 2025, Optimizely unveiled the next evolution of Optimizely Op...

Graham Carr | Dec 16, 2025