Databases
A database is an independent graph inside your organization: its own nodes, relationships, indexes and constraints. Queries always name one database, and a query never sees another database’s data.
Use databases to separate environments (staging, production), tenants of
your own product (tenant-acme, tenant-globex), or unrelated graphs. They
cost nothing extra: you pay for what they store and the requests they serve.
Creating one
From the console (Databases → Create database), the
management API
(POST /databases), the SDKs’ ManagementClient, the
CLI (namidb databases create) or
Terraform (namidb_database).
Names:
- lowercase letters, numbers,
-and_; - start with a letter or a number;
- at most 63 characters;
- unique in the organization;
backups,exportsandtenants, and names starting withnmdbexp-, are reserved.
A name you just deleted is free again once the old data has been erased
(409 name_purging until then, usually within minutes).
Status
| Status | Meaning |
|---|---|
ready | Serving queries. |
restoring | Being filled from a backup (a restore, clone or point-in-time restore). Queries answer 503 database_unavailable until it is ready. |
failed | The restore that was creating it failed. Delete it and try again. |
A database also reports read_only (see below) and its endpoints: the HTTP
URL and the Bolt URI to query it with.
How many
| Plan | Databases |
|---|---|
| Free | 2 |
| Pro | 20 |
| Scale | 100 |
| Enterprise | Set in your agreement |
Restores, clones and point-in-time restores create a new database, so they
count against the same limit (403 plan_limit when it is reached).
Over the limit after a downgrade
Nothing is deleted when you move to a plan with fewer databases. The newest
databases past the new limit become read-only: queries still work,
writes answer 429 plan_limit with the database’s name, and the console and
the API show read_only: true. Delete a database, or upgrade again, and the
next one becomes writable.
Deleting one
Owners, admins and developers delete a database from its page, or with
DELETE /databases/{database}. Deleting:
- refuses new queries to it within seconds;
- revokes API keys that were scoped to that database only (keys that also reach other databases keep working for those);
- erases its data in the background.
Backups taken before the deletion are kept until they expire under the plan’s
retention. If you kept a backup’s id, POST /restores can still restore it
into a new database. Otherwise deleting a database cannot be undone: take an
export or a clone
first if you might need it again. At most 20 databases per organization can
be deleted per hour.
One engine, many databases
All databases of an organization are served by the organization’s own engine, which starts on demand and stops when idle (see Scale to zero). The plan’s limits on requests per second, concurrent queries and Bolt sessions apply to the organization as a whole, across its databases. See Rate limits.