Skip to main content

Open-source database technologies

If you haven't yet taken a look at our High Availability Database Clusters documentation, we recommend you check that out first. It contains an outline of how databases work on the OpenShift platform and why it's important to use highly-available databases. All the technologies discussed here are highly-available.


Postgres is the most common database running on the OpenShift platform. It is not highly available on its own, so teams use Patroni or CrunchyDB. These are both ways to deploy Postgres in a highly-available way.

Postgres is a relational database. If a non-relational database would better suit your application's needs, consider MongoDB instead.

Patroni is the most common highly available solution on the platform. It is very well-supported by the development community in the BC Government. However, it is older and less flexible than the CrunchyDB Operator. You can find a Platform Team supported image for Patroni at

CrunchyDB is easier to implement and has many more powerful functions than Patroni. It's also more resilient to failure than Patroni. However, since it is new, there are currently fewer community-created tools and templates for CrunchyDB. The operator includes its own image to ensure the best possible compatibility, so the Platform Team does not provide an image for use with the operator. We recommend that you read through the official CrunchyDB documentation to get a full understanding of the features offered by the operator.


MongoDB is the next most common database. It has built-in HA capabilities, and you can find an example of how to deploy a Mongo replica set on GitHub.

MongoDB is a non-relational database. If a relational database would better suit your application's needs, consider Postgres instead.

You can find a Platform Team supported image for MongoDB at


Redis technically isn't a database at all. It's an in-memory datastore that stores data in key-value pairs.

You can think of Redis data as being stored in data structures similar to those commonly found in many programming languages, like dictionaries.

Because it keeps the data in-memory, it is very fast but requires a lot of memory to run. It's best used for very small datasets that need to be accessed very quickly. Despite being an in-memory datastore, it's still able to store its data on-disk, which means you can use persistent volume claims (PVCs) on OpenShift to ensure that the data will persist after the pod restarts. It also has fewer of the strict limitations placed on most databases.

A useful Redis image is included in the openshift namespace by default. This image is provided by RedHat and is not supported by the Platform Team.