◆
Ready immediately
Ask for a database and receive one, with a host, a user and a password. There is no provisioning queue and no window where it half exists.
Most managed databases are a form, a wait, and a support ticket when the connection string does not work. This one answers with credentials you can paste into your application before you have finished reading this sentence.
Two databases and 40 GB included, with no card required to begin.
What teams put in it
A database is infrastructure. The less of it you have to hold in your head, the more of your attention goes to what you are building on top of it.
Ask for a database and receive one, with a host, a user and a password. There is no provisioning queue and no window where it half exists.
Separation between tenants is enforced by the database itself, not by application code remembering to filter. It can be demonstrated, not merely asserted.
The password is shown once, at creation, and we keep only a hash of it. We cannot read it back to you, which is the point.
Replace a credential and the old one stops working immediately. No coordinated restart, no window where both are valid.
Size is read from the database when you open the page, not from a number written down the last time somebody remembered to update it. The figure you see is the figure the engine reports.
It is rarely the database that takes the time. It is the account, the network rules, the parameter group, the credential rotation policy, and the person who knows how all four fit together.
Each database is a separate space with its own user, and that user is granted its own space and nothing else. A query against another tenant does not return the wrong rows — it is refused by the engine before it runs.
Anything that speaks the protocol connects. No proprietary driver and no wrapper.
Because a password you can retrieve from a dashboard is a password everyone with the dashboard has.
If provisioning cannot complete, the record is removed with it. No orphans to clean up later.
At the moment you create, not after the fact. You are told you are at the limit instead of discovering it from an invoice.
We moved fourteen services onto it in an afternoon. The part I keep telling people about is that nobody had to ask anyone for anything.
Seconds. You are given a host, a database name, a user and a password, and the database accepts a connection immediately. There is no state in which it exists but will not answer.
Each database has its own user, granted access to its own space and nothing beyond it. The separation is enforced by the database engine rather than by application code, so it holds regardless of what any application does.
The password is shown once when it is created and only a hash is stored, so it cannot be read back by us or by anyone with access to our records. Your data is yours; we operate the platform it sits on.
The replacement is issued and the previous one stops working at that moment. There is no overlap window, which means no period in which a leaked credential still opens the door.
Two databases and 40 GB of storage. The console shows what you are using against that, and the limit is applied when you create rather than discovered on a bill.
The database, its storage and its user are all removed. Nothing is retained, and the credential that reached it stops working.
Create a database, copy the connection string, and get back to what you were doing.
Two databases and 40 GB included. No card to begin.