Guides - Database Engines and Plans

Fully managed cloud database clusters built on top of Linode’s trusted and reliable platform.

Create a Linode account to try this guide with a $ credit.
This credit will be applied to any valid services used during your first  days.

When deploying a Managed Database, you are able to select from a variety of database engines and plans. While each database engine enables you to store data, application compatibility and the way in which they store and access data can vary greatly. This guide aims to provide more information on each database engine, the reasons you might choose one over the other, and advice on selecting an appropriate plan size.

Database Engines

The following database engines are available on Linode’s platform:

MySQL

Starting at $15 ($0.0225/hr) for a single node and $35 ($0.0525/hr) for a 3 node high availability cluster.

MySQL is an industry standard relational database management system (RDMBS) that uses the SQL query language. Compared to other databases, it’s relatively easy to use and its large community means there are lots of online resources available. MySQL values performance and accessibility over pure SQL compliance, so its syntax can slightly differ from strict SQL. Many popular applications (including WordPress) require MySQL or a MySQL compatible database.

Best for general-purpose websites and applications, e-commerce sites, applications employing LAMP or LEMP stacks, and for beginner database developers looking for robust online resources

Available versions:

  • MySQL 8.0
  • MySQL 5.7

PostgreSQL

Starting at $15 ($0.0225/hr) for a single node and $35 ($0.0525/hr) for a 3 node high availability cluster.

PostgreSQL is an object-relational database management system (ORDBMS) that can use SQL. It’s generally more flexible and feature-rich than MySQL, though it’s not a drop-in replacement and applications need to have built-in support for it. It also has support for more data types, including JSON, and adopts some features of NoSQL databases. While PostgreSQL is generally more challenging to implement, it can support more advanced queries and is a popular choice for enterprise applications.

Best for experienced SQL developers, applications that perform complex queries, using PostgreSQL-specific features, and for business users looking for dedicated commercial support.

Available versions:

  • PostgreSQL 14
  • PostgreSQL 13
  • PostgreSQL 12
  • PostgreSQL 11
  • PostgreSQL 10

Database Plans

Each Managed Database can be deployed with a specific set of resources. This collection of resources is called the plan. Linode offers two plan types for Managed Databases:

Shared CPU Instances

1 GB - 192 GB Memory, 1 - 32 Shared vCPU Cores, 25 GB - 3840 GB Storage

Shared CPU Instances offer a balanced array of resources coupled with shared CPUs that can burst up to 100% for short intervals. This keeps costs down while still supporting a wide variety of cloud applications. Your processes are scheduled on the same CPU cores as processes from other Compute Instances and Managed Databases. This shared scheduling is done in a secure and performant manner and Linode works to minimize competition for CPU resources between your server and other servers.

Best for development servers, staging servers, low traffic websites, personal blogs, and production applications that may not be affected by resource contention.

Dedicated CPU Instances

4 GB - 512 GB Memory, 2 - 64 Dedicated vCPUs, 80 GB - 7200 GB Storage

Dedicated CPU Instances reserve physical CPU cores that you can utilize at 100% load 24/7 for as long as you need. This provides competition free guaranteed CPU resources and ensures your software can run at peak speed and efficiency. With Dedicated CPU instances, you can run your software for prolonged periods of maximum CPU usage, and you can ensure the lowest latency possible for latency-sensitive operations. These instances offer a perfectly balanced set of resources for most production applications.

Best for production websites, enterprise applications, high traffic databases, and any application that requires 100% sustained CPU usage or may be impacted by resource contention.

Note
Once a Managed Database cluster is created, it cannot be resized to a different plan. To modify the resources allocated to your database, you will need to create a new Managed Database with the desired plan, migrate your data, and delete the original Managed Database.

This page was originally published on


Your Feedback Is Important

Let us know if this guide was helpful to you.