Database guides

SingleStore

Updated 2026-08-01 · 2 min read

Real-time distributed SQL on the MySQL wire — rowstore and columnstore in one engine, with AddisDB’s full MySQL toolset on top.

SingleStore speaks the MySQL wire protocol, so AddisDB drives it with the MySQL driver on port 3306 — introspection, in-grid editing, live monitoring and mock data all work.

Who it is for

SingleStore is built for workloads where the answer has to be current: live dashboards, operational analytics, fraud and personalization scoring. It keeps a rowstore for fast writes and point lookups and a columnstore for scans, so ingestion and aggregation can share one system.

A cluster is aggregator nodes that plan and leaf nodes that store shards. Tables are distributed by a shard key you choose, and a join between two tables sharded on the same key stays local to each leaf — pick a different key and the same join becomes a network shuffle.

Consider it when you are streaming data in continuously and querying it immediately, and a nightly warehouse load would be too late to be useful.

Set up the workspace

  1. On SingleStore Helios, create a workspace group and a workspace.
  2. Open the workspace’s Connect panel and copy the endpoint host.
  3. Set or reset the admin password — this is what you will paste into AddisDB.
  4. Under Firewall, allow your IP address. New workspaces block everything by default.
  5. Local: the singlestore/cluster-in-a-box Docker image runs a full cluster on 3306.
# A single-container cluster for local work
docker run -d --name singlestore \
  -e ROOT_PASSWORD=secret -e SINGLESTORE_LICENSE=<your-free-licence> \
  -p 3306:3306 -p 8080:8080 singlestore/cluster-in-a-box

Connect from AddisDB

  1. New Connection → SingleStore. Port prefills to 3306 and the username to root.
  2. Paste the endpoint host and your admin password. Set Database to the database you want open by default (information_schema is prefilled if you just want to look around).
  3. Set SSL mode to require for Helios.
  4. Test, then Save.

Reading a distributed schema

Two clauses in a SingleStore table definition decide almost everything about how it performs: SHARD KEY, which spreads rows across leaves, and SORT KEY, which orders a columnstore segment on disk. AddisDB shows you the definitions as the server reports them rather than reconstructing them, so those clauses survive into what you read.

What AddisDB gives you

  • Schema introspection with the foreign-key diagram and ⌘K search across every object.
  • In-grid editing behind the Edit toggle.
  • Live Monitor over the MySQL-compatible views — active queries, sessions and connection stats.
  • Mock data generated from your real schema.
  • AI querying and one-click repair of failing SQL.
  • The Chart view for aggregations, and the full safety model.