OLTP mode (coming soon)
Coming soon to Databasin Sail: OLTP mode, a managed PostgreSQL database beside your cluster for apps, queryable from Sail as a live catalog.
OLTP mode will add a managed PostgreSQL database beside your Sail cluster: a transactional database for apps that read and write single rows fast, which you can also query from Sail next to your lakehouse tables.
OLTP mode is coming soon and isn't available yet. The Sail cluster card and the create dialog show an OLTP mode switch marked Coming soon, and it can't be turned on. Everything below describes what we're building, and details can change before it ships.
What it will be
- One PostgreSQL 17 database per Sail cluster, run as Azure Database for PostgreSQL Flexible Server.
- A switch on the cluster card. Off by default; turn it on when you create the cluster or later.
- A real transactional database. Reads and writes, transactions and indexes, for apps that need them.
- A connection panel with the host, port, database, user, password, a JDBC URL and a
psqlcommand, so any Postgres driver can connect. Connections require SSL. - The same network access as the cluster. On Databasin Cloud: Private, Specific IPs or Open, as you set on the cluster.
- Always running. The database stays on, unlike Sail workers, which sleep when idle.
Two ways in
| Who | How they reach it |
|---|---|
| Your apps | Directly, with the connection details and any Postgres driver. Full reads, writes and transactions. |
| Analysts, notebooks and BI tools | Through Sail, as a live catalog named oltp, joinable with lakehouse tables. |
From Sail, the database will look like any other live source, and your access rules decide who can query it:
-- Coming soon: the OLTP database appears in Sail as the live catalog `oltp`
SELECT o.region, sum(o.amount) AS today, avg(h.daily_amount) AS typical_day
FROM oltp.public.orders o
JOIN sandbox.sales.daily_totals h ON h.region = o.region
WHERE o.created_at >= current_date
GROUP BY o.region;
At first, Sail reads from the database and your apps write to it. Writing to it from Sail comes later.
Sizes
| Size | vCPU | Memory | Storage |
|---|---|---|---|
| Basic | 1 | 2 GB | 32 GB |
| Small | 2 | 4 GB | 64 GB |
| Medium | 2 | 8 GB | 128 GB |
| Large | 4 | 16 GB | 256 GB |
| XLarge | 8 | 32 GB | 512 GB |
Basic and Small are burstable, meant for apps and light use rather than sustained load. You'll be able to resize later; storage only grows.
How it will roll out
| Phase | What you'll be able to do |
|---|---|
| 1. The database | Turn OLTP mode on, pick a size, connect apps, query it from Sail as oltp, resize, turn it off. |
| 2. Load and unload | Copy a Postgres table into the lakehouse in one step, and load lakehouse tables into Postgres. |
| 3. Sync to the lake | Keep a Postgres table copied into the lakehouse on a schedule, and later continuously as rows change. |
| Later | Writes from Sail into the database, a high-availability standby, and separate Postgres logins per user. |