Use case · Databases
MySQL hosting
MySQL is one of the most widely used open-source relational databases, popular for web applications. Hosting it well means tuning its InnoDB buffer pool and memory, providing fast storage, and setting up replication for availability. Open-source, with the compatible MariaDB fork, self-hosted on dedicated EU hardware it gives control, performance, and European sovereignty.
Key points
- MySQL is among the most widely used open-source relational databases, especially for the web.
- Its InnoDB storage engine provides transactions and integrity; its buffer pool is the key memory cache.
- Tuning the InnoDB buffer pool to available memory is central to MySQL performance.
- MariaDB is a widely-used, highly-compatible community fork of MySQL.
- Self-hosting on EU hardware gives control and European sovereignty over the data.
What is MySQL, and why host it?
MySQL is one of the most widely used relational databases in the world, an open-source system especially popular for web applications. It has long been a default choice for web development, forming part of the common stack behind a great many websites and applications, and it powers widely-used software across the web. MySQL is valued for being capable, fast for common workloads, well-understood, and open-source, with an enormous base of users and a wealth of accumulated knowledge around it. This popularity and maturity make it a dependable, familiar choice for applications needing a relational database.
Hosting MySQL well means providing infrastructure suited to how it works and to the demands of a database that often underpins busy web applications. Like any database, MySQL benefits from fast storage, ample memory, and reliable hosting, and it has particular characteristics — in its storage engine, its memory use, and its replication — that reward hosting attuned to them. This page focuses on MySQL specifically; the general considerations of database hosting apply and are covered on the database-hosting page, while what follows attends to what is particular about running MySQL.
MySQL and MariaDB
Alongside MySQL is MariaDB, a community-developed fork of MySQL created by members of its original development community, which is widely used and highly compatible with MySQL. MariaDB arose to continue MySQL's open-source development independently, and it remains largely compatible, so that in many cases it can be used in place of MySQL with little or no change. This gives users a choice between MySQL and MariaDB, both open-source, both widely used, and both serving the same broad role, with differences in development, some features, and governance.
For hosting purposes, MySQL and MariaDB are similar enough that much of what applies to one applies to the other, while the choice between them is a real decision for the user. Both benefit from the same kinds of hosting — fast storage, ample memory, appropriate tuning, and replication — and both are open-source, self-hostable databases in the MySQL family. The choice depends on preferences around features, development direction, and compatibility with what an application expects. We host both MySQL and MariaDB, since they share the same hosting needs and the choice between them is the user's; what follows applies broadly to both, referring to MySQL for simplicity.
Storage engines and InnoDB
A distinctive aspect of MySQL is its storage-engine architecture, in which the engine that actually stores and manages data can be chosen, with InnoDB being the standard and default choice. InnoDB provides transactions, adherence to the properties that keep data reliable, and row-level locking that suits concurrent access, making it the appropriate engine for most applications needing a dependable relational database. The storage engine determines important characteristics of how data is stored, locked, and kept consistent, and InnoDB's transactional, integrity-preserving design is why it is the default for serious use.
Understanding that InnoDB is the engine behind most MySQL databases clarifies much about hosting MySQL, because InnoDB's behaviour and tuning are central to MySQL performance. The way InnoDB uses memory and storage, and how it is configured, largely determines how a MySQL database performs, so hosting MySQL well means attending to InnoDB in particular. Other engines exist for particular purposes, but for the transactional, reliable databases most applications need, InnoDB is the engine, and its characteristics shape how MySQL should be hosted and tuned. We host MySQL with attention to InnoDB, since it is where most of the performance-relevant behaviour lies.
Memory and tuning for MySQL
The single most important tuning setting for MySQL performance is usually the InnoDB buffer pool — the memory InnoDB uses to cache data and indexes — because serving data from this cache is far faster than reading from storage. Sizing the buffer pool to use a large share of the server's memory, so that as much of the active data as possible is held in memory, is central to MySQL performing well; a buffer pool too small for the workload forces frequent slow storage access, while a generous one keeps the hot data in memory. This makes ample memory and a well-sized buffer pool the foundation of MySQL performance for most workloads.
Beyond the buffer pool, MySQL has other settings that reward tuning to the workload and hardware, but the memory dedicated to InnoDB's caching is usually the dominant factor. Providing a server with generous memory and configuring the buffer pool to use it well is the first and most impactful step in hosting MySQL for performance. We provide ample memory and size the InnoDB buffer pool to the hardware and workload, because a MySQL server with a large, well-configured buffer pool serving data from memory performs markedly better than one starved of cache memory. Getting this right is much of what distinguishes well-hosted MySQL from a poorly-tuned instance.
Storage and replication
MySQL performs many storage operations and relies on storage for durability, so fast, reliable storage matters, and fast NVMe storage suits it by providing the throughput and input/output operations its reads and writes need. Even with a large buffer pool holding hot data in memory, writes must be persisted to storage for durability, and data not in the cache must be read from storage, so storage speed affects performance and durability both. Fast, reliable NVMe storage underpins MySQL's performance and the safety of its data.
For availability, MySQL provides replication, maintaining copies of the database on replica servers that can take over if the primary fails. MySQL replication keeps replicas updated from the primary, so that a replica holds a current copy and can be promoted to primary if the original fails, keeping the database available; replicas can also serve read queries to spread read load. Setting up replication and failover suits databases that must stay available through server failures. When we host MySQL, we provide fast storage for its performance and durability, and replication for availability where the workload requires it, using MySQL's own replication to keep the database available.
Self-hosted MySQL and sovereignty
MySQL and MariaDB being open-source makes self-hosting them attractive, giving control over the database and, on EU infrastructure, sovereignty over its data. Being open-source, they can be self-hosted without licensing cost for the common open-source editions, so the cost is the infrastructure and operation, and self-hosting gives full control over the database, its configuration, and its data. This makes self-hosting MySQL or MariaDB on infrastructure you control an appealing way to run a capable, widely-used database on your own terms.
Self-hosting on EU infrastructure adds European sovereignty over the database's data. VV Internet Hosting is incorporated in the Netherlands, within the EU, so a MySQL or MariaDB database self-hosted with us keeps its data under European jurisdiction and outside the direct reach of the US CLOUD Act, on infrastructure you control. For databases holding personal, sensitive, or regulated data, keeping the data in the EU on controlled infrastructure keeps it under European law and in your hands. The combination — a widely-used open-source database, self-hosted with control and European sovereignty — suits organisations that want a familiar, capable database on their own terms and under European jurisdiction.
MySQL or PostgreSQL, and where VV Internet Hosting fits
MySQL and PostgreSQL are the two most prominent open-source relational databases, and the honest position is that both are excellent, suited to somewhat different preferences rather than one being simply better. MySQL is prized for its wide use, familiarity, and strong performance on common web workloads, with an enormous ecosystem around it; PostgreSQL is prized for its rich feature set, standards compliance, and extensibility. Many applications would run well on either, and the choice often comes down to what an application already expects, team familiarity, and which system's particular strengths matter for the workload. We host both and will not pretend one is universally superior.
We host dedicated infrastructure for self-hosting MySQL and MariaDB: fast NVMe storage, ample memory sized for the InnoDB buffer pool, dedicated resources free of noisy neighbours, and support for replication — in EU datacenters under European jurisdiction. This suits organisations self-hosting MySQL or MariaDB that want performance, control, and European data sovereignty. We are clear about our limits: we provide the dedicated infrastructure you run the database on, not a fully managed MySQL service that administers it for you. If you want a fully managed database, that is a different offering. We are the dedicated, sovereign infrastructure on which you self-host MySQL or MariaDB — and if that fits your needs, we can host it well.
Related use cases
See also
Questions
MySQL, answered plainly
Common questions about hosting for MySQL.
What is the difference between MySQL and MariaDB?
MariaDB is a community-developed fork of MySQL, created by members of its original development community to continue open-source development independently. It remains largely compatible with MySQL, so in many cases it can be used in place of it with little change. Both are open-source and widely used; they differ in development, some features, and governance. We host both.
What matters most for MySQL performance?
Usually the InnoDB buffer pool — the memory InnoDB uses to cache data and indexes. Serving data from this cache is far faster than reading from storage, so sizing the buffer pool to hold as much of the active data in memory as possible is central to MySQL performing well. Ample memory and a well-sized buffer pool are the foundation, alongside fast storage.
Should I choose MySQL or PostgreSQL?
Both are excellent open-source relational databases suited to somewhat different preferences. MySQL is prized for wide use, familiarity, and strong performance on common web workloads; PostgreSQL for its rich features, standards compliance, and extensibility. Many applications run well on either; the choice often comes down to what your application expects and which strengths matter. We host both.
Planning MySQL infrastructure?
We host dedicated, EU-sovereign infrastructure sized to your workload — and we will tell you plainly when something else fits better. Tell us what you're building.