YugabyteDB

YugabyteDB’s YSQL API is built on the actual PostgreSQL query layer, not a reimplementation of it. AddisDB connects with the Postgres driver on YSQL’s default port 5433, and because the pg_stat_* views are genuinely there, the Live Monitor works.

Who it is for

Yugabyte is for teams that want distributed, horizontally scalable SQL while keeping Postgres compatibility as close to literal as possible — extensions, syntax, drivers and the catalog all behave the way your Postgres code expects.

The architecture splits the two halves: the query layer is Postgres source, and underneath it DocDB shards and replicates data with Raft. That is why the catalog looks so familiar while the storage behaves nothing like a single node’s.

It suits a Postgres application that has outgrown a single primary, or a deployment that needs to span regions. If your Postgres app is comfortably served by one node, you do not need it.

Set up the cluster

1. On YugabyteDB Aeon (the managed service), create a cluster and add your IP address under Network Access.
2. Download the cluster CA certificate when prompted, and create a database user — the credentials are shown once.
3. Open the Connect dialog and note the host; YSQL listens on 5433, not 5432.
4. Self-hosted or local: yugabyted start gives you a single node with YSQL on 5433.

# A local single node, YSQL on 5433
yugabyted start --advertise_address=127.0.0.1

Connect from AddisDB

1. New Connection → YugabyteDB. Port prefills to 5433, database to yugabyte and username to yugabyte.
2. Fill in the host from the Aeon Connect dialog and the user you created.
3. Set SSL mode to require (or verify-full if you downloaded the CA certificate).
4. Test, then Save.

Yugabyte exposes two APIs from the same cluster. AddisDB’s YugabyteDB engine speaks YSQL, the Postgres-compatible one. If the data you are after lives in YCQL instead, connect with the Cassandra engine — YCQL speaks the CQL protocol on port 9042.

What AddisDB gives you

• Full introspection and the foreign-key schema diagram.
• In-grid editing behind the Edit toggle.
• Live Monitor with real active queries, sessions, locks and connection stats — Yugabyte carries the genuine pg_stat_* views.
• Mock data from your real schema, plus AI querying and query repair.
• ⌘K search, the Chart view, and the full safety model.

Designing for a distributed cluster

Two habits carry over from Cockroach and matter just as much here: monotonically increasing primary keys concentrate writes on one tablet, and a transaction spanning many tablets pays consensus latency per participant. Yugabyte gives you HASH and RANGE sharding on the primary key clause to control which one you get.