Payments are experiencing issues due to temporary restrictions in Russia. If your payment does not go through, please submit a support request.Our support team is available 24/7 — we are always here to help with hosting and server issues.We are now accepting requests for dedicated server rental and colocation services in our data center.Reminder: we recommend enabling backups for additional data protection.A new VPS/VDS lineup with NVMe storage and improved performance is now available.Maintenance work on some servers has been completed. All services are operating normally.
Article3 min read

Yandex Cloud Adds Database Presets: Why a Ready-Made Configuration Is Just the Start of Store Setup

The September digest introduced ready-made options for managed databases. I explain how to evaluate such a configuration based on the catalog, orders, and data exchange.

Server equipment behind a perforated cabinet door
In this article

Choosing a database starts with difficult questions: how much memory to allocate, whether a standby machine is needed, and which disks are suitable? A ready-made configuration lowers the entry barrier, but it cannot account for the specifics of a particular catalog or the load on the store.

On September 7, 2026, Yandex Cloud announced in its product digest that presets are now available for five managed database services. For MySQL, for example, options are presented for different usage scenarios. This is a convenient starting point that must then be tested against your own application.

The preset name is not the result of a test

A "fast" or "reliable" configuration describes the proposed set of parameters. It does not guarantee a specific checkout time. Stores with the same number of products can execute completely different queries.

Load is influenced by catalog structure, the number of offers, filters, pricing rules, and background operations. Additionally, the application may maintain too many connections or repeat the same query. These specifics do not disappear simply by selecting a more expensive option.

Before migrating a database, verify application compatibility with the installed DBMS version. General support for MySQL does not cover all limitations specific to a CMS, its modules, or connection settings.

Compare during real-world operations

A useful check involves more than viewing pages; it requires placing orders, updating stock levels, and synchronizing the catalog. Only simultaneous read and write operations can reveal latency that remains hidden in idle tests.

Monitor query execution times, lock wait durations, connection counts, and disk subsystem behavior. Business owners do not need to interpret every graph, but contractors must link metrics to tangible operations, such as explaining why a customer experiences delays during cart confirmation.

Maintain identical conditions for comparison. If you change the server, queries, and caching simultaneously, it becomes impossible to determine which factor drove the results or what will be needed during future growth.

Managed databases do not eliminate all responsibilities

The provider maintains the infrastructure defined by the service, while the site team remains responsible for the application and correct data handling. Clarify support boundaries, backup procedures, recovery processes, and behavior during failover to a standby node.

I would include a short action plan in the acceptance criteria for database unavailability: who receives the alert, who investigates the error, and how incomplete orders are verified. A preset is useful because it accelerates the launch. Stable store operation is ensured by monitoring, clear accountability, and tested recovery scenarios.

Discussion0

Share your experience and ask questions. Comments without links appear after editorial review.

No comments yet. Start the discussion.