On this page
Managed databases (DBaaS)
Managed databases let you create a ready-to-use database instance in a few clicks. Patrii Cloud provisions and runs the underlying server so you can focus on your data instead of installing, patching and tuning a database host.
Instead of launching an instance and installing a database engine by hand, you choose an engine, a version, a size and a disk, and Patrii provisions a managed instance for you. The compute and storage underneath are handled for you, and the console shows the connection details your application needs.
Managed databases are in beta. The available engines, versions and options may change as the service matures, so try it on non-critical workloads first and keep your own backups of anything important.
Key concepts
Database instance — A managed server running one database engine, with its own compute, storage and connection endpoint.
Engine (datastore) — The database software the instance runs; the choices offered come from the console.
Version — The specific release of the chosen engine.
Size (flavor) — The CPU and memory allocated to the instance.
Storage size — The disk capacity for your data, set when you create the instance.
Before you start
- Enough quota for the instance size and storage you choose.
- A client or application that speaks the chosen engine's protocol.
- Network access from your application to the instance's endpoint.
Step by step
- Open the create wizard
Go to Databases and choose Create database.
Screenshot — The Create database button on the Databases pageThe Create database button on the Databases page - Pick an engine and version
Choose a database engine and one of its available versions.
Screenshot — The engine and version selection stepThe engine and version selection step - Name it and choose a size
- Give the instance a recognizable name.
- Select an instance size for your workload.
- Set the storage size for your data.
- Optionally set an initial database name.
Screenshot — The instance name, size and storage stepThe instance name, size and storage step - Create and wait until available
Review the summary and create. The instance provisions and moves to an available state after a short time.
Screenshot — A database instance transitioning to the available stateA database instance transitioning to the available state - Connect your application
Open the instance to read its connection details, then put the host, port and credentials into your application's configuration.
Screenshot — The database detail page showing connection detailsThe database detail page showing connection details
Examples
# use the host, port and credentials from the console HOST=<db-host-from-console> PORT=<db-port-from-console> # then connect with your engine's own client, e.g. # <engine-client> --host $HOST --port $PORT -u <user> -p
DATABASE_URL=<engine>://<user>:<password>@<db-host-from-console>:<port>/<database>
Limits & specifications
What you can do with a managed database:
| Capability | What it does |
|---|---|
Create | Provision a new managed database instance. |
List | See your instances with their engine, size and status. |
View details | Read connection details and instance information. |
Delete | Remove an instance you no longer need. |
Best practices
- Keep your own backups of important data while the service is in beta.
- Store connection credentials as secrets or environment variables, never in source control.
- Restrict network access so only your application can reach the database endpoint.
- Size storage with headroom for growth so you do not run out unexpectedly.
- Test a version change on a throwaway instance before applying it to anything you depend on.
FAQ
Which database engines are available?
Where do I find my connection details?
My application cannot reach the database.
Is managed databases production-ready?
Learn more
Everything you can do here in the console is also available through the Patrii Cloud API for automation and scripting.