Databend

Databend is an open-source, cloud-native data warehouse written in Rust that separates storage from compute and keeps its data in object storage. It exposes a MySQL-compatible handler, so AddisDB connects with its MySQL driver — on port 3307, Databend’s default for that handler, rather than 3306.

Who it is for

Databend suits teams who want Snowflake-shaped economics on their own object storage: compute that scales independently and can be shut off entirely, with data sitting in S3 or a compatible store rather than in the database’s own files.

Because storage is remote, the first query against cold data pays for fetching it. That is expected behaviour rather than a fault, and it is why Databend caches aggressively at the compute layer.

Set up the warehouse

1. Note the host of a databend-query node, or your Databend Cloud endpoint.
2. Use port 3307 for the MySQL handler. Databend also has an HTTP handler on 8000, which is a different interface.
3. The default account on a local install is root with no password. On Databend Cloud, create a SQL user and note its password.
4. Note the database — default is the one a fresh install starts with.

# Databend’s MySQL handler listens on 3307
mysql -h databend.example.com -P 3307 -u root -e 'SELECT version();'

Connect from AddisDB

1. New Connection → Databend. Port prefills to 3307 and username to root.
2. Enter the host and credentials, and the database name.
3. Set SSL mode to require for Databend Cloud; leave it at prefer for a local instance.
4. Test, then Save.

What AddisDB gives you

The Big Data Console, since Databend is catalogued as a warehouse engine, plus the results grid, exports and saved queries.

The schema tree reads information_schema, which Databend implements, so databases, tables and columns load normally.

Query plans use Databend’s own EXPLAIN and render as text.