
ALT QuestDB banner titled 'Materialized views, no aggregation.', tagged 10.2 · Enterprise 4.2, with a pill reading passthrough, one output row per base row. Body text reads: a narrower copy of the table, kept current as rows arrive. Pick the columns, filter to one symbol or one venue. On the right, under 'a passthrough view,' chips read no SAMPLE BY, columns you choose, filtered rows, and SYMBOL INDEX kept. Under 'expire rows,' a pink panel lists three forms: EXPIRE ROWS WHEN expiry < now(), a condition checked on every read; EXPIRE ROWS KEEP LATEST ON timestamp PARTITION BY sensor_id, the newest row per key; and EXPIRE ROWS KEEP 10 HIGHEST ON amount PARTITION BY symbol, the ten largest per symbol. A footnote reads: a timestamp condition also deletes from disk. Otherwise, add a TTL.

ALT A line chart from a QuestDB Web Console dashboard: broker and OTC markout curves by counterparty type, plotted from 30 minutes before the trade to 60 minutes after, with basis points on the vertical axis. The lines for industrial and utility counterparties drift downwards after the trade, while the lines for banks and traders drift upwards, so trades against industrials and utilities look progressively worse as time passes.

ALT QuestDB banner titled 'DEDUP SKIP, first write wins.', tagged SQL · Deduplication, with a pill reading DEDUP SKIP KEYS, ON CONFLICT DO NOTHING. Body text reads: a second dedup mode. Replays after a reconnect are discarded, and the original row keeps the values it arrived with. On the right, under 'a client replays a row after reconnect,' two cards compare modes. DEDUP UPSERT KEYS, latest write wins: received_at 10:02:41, overwritten with the resend time. DEDUP SKIP KEYS, first write wins, highlighted in pink: received_at 10:00:03 in green, duplicate discarded, original kept. A footnote reads: cheaper per duplicate, on Parquet only timestamp and keys are decoded. ALTER TABLE ... DEDUP ENABLE SKIP KEYS(...), no rewrite.

ALT QuestDB Enterprise banner titled 'dbt models, in QuestDB SQL.', tagged Enterprise · dbt-questdb, with a pill reading dbt-questdb, adapter over QWP. Body text reads: build, test and document models with SAMPLE BY, LATEST ON or ASOF JOIN, over QWP. On the right, under 'materialized as a materialized view,' a pink panel reads: the database keeps it current, instead of dbt rebuilding it on a schedule, with refresh chips for immediate, every 10m, period and manual. Under 'config that speaks QuestDB,' cyan chips read timestamp, partition_by, symbols, dedup_upsert_keys and ttl. Under 'all materializations': views, tables, incremental, seeds, snapshots, ephemeral.

ALT QuestDB community blog banner titled 'Port congestion, from public AIS.', with a pill reading Urtzi Alfaro, Port Context Engine. Body text reads: which vessels wait at anchor, for how long, when they reach a berth, and how that compares with the previous 90 days. On the right, under 'four ports so far,' four rows list Rotterdam marked live, Antwerp-Bruges and Piraeus marked pilot, and Hamburg marked calibrating. Under 'what was true at time T,' pink chips read LATEST ON, ASOF JOIN, SAMPLE BY, DEDUP UPSERT KEYS and TTL. A footnote reads: 5 Go services, NATS JetStream, one QuestDB container on one VPS, 2 CPUs, 1 GB.

ALT QuestDB banner for FOSDEM 2027, Brussels, January 30, titled 'QuestDB + OpenC3 COSMOS at FOSDEM 2027.' A pill reads: joint stand, QuestDB and OpenC3 COSMOS. Body text reads: one joint stand, a working desktop CubeSat, and core engineers from both projects. Come and find us. On the right, a line drawing of a small cube satellite with two solar panels and an antenna sends signal arcs toward a pink telemetry trace labeled 'telemetry, live'. Below, three boxes linked by arrows read CubeSat, COSMOS 7 and QuestDB. Under 'every measurement it ever reported,' two green chips read SAMPLE BY and ASOF JOIN. A footnote reads: January 30, Brussels.

ALT QuestDB banner titled 'ADBC drivers for QuestDB.', tagged Integrations · adbcBridge, with a pill reading adbcBridge, third-party. Body text reads: Arrow from C#, Java, Go, TypeScript, or any tool that takes an ADBC driver. On the right, under 'our own arrow clients,' grey chips read C / C++, Rust, Python and Ruby. Under 'adbcBridge reaches,' pink chips read C#, Java, Go, TypeScript and any ADBC tool. Under 'two flavours,' two cards: QuestDB 10+, native QWP driver, Arrow batches for reads and bulk ingest; and QuestDB 9 or older, ODBC bridge over PGWire, also the pick when one driver serves several databases.

ALT QuestDB blog banner titled 'A trading day, replayed in 32.5s.' Body text reads: 353M rows of US equities top of book, streamed into Python as Arrow. The network ran out before the database did. On the right, a bar chart of market activity across the day, with a white playhead partway through: bars to its left are pink, already replayed, and bars to its right are grey, still to come.

ALT QuestDB banner titled 'QuestDB, in Ruby.', tagged New client · Ruby, with a pill reading gem install questdb. Body text reads: a new client, published as the questdb gem. QWP over WebSocket, both ways, written the way Ruby is written. On the right, under 'written the way Ruby is written,' a diagram shows Ruby connecting to QuestDB with an arrow labelled QWP over WebSocket, captioned 'Keyword args. Time as a timestamp. I/O without the GVL.' Under 'both ways,' three rows read: Write, rows, column arrays, or Arrow from Polars. Read, Enumerable, Polars, nanoarrow, Red Arrow. Blocks, leases released on the way out, even on raise. A footnote chip reads Threads: ingestion threads overlap

ALT QuestDB banner titled 'QuestDB, from the browser.', tagged New client · Browser, with a pill reading @questdb/browser-client. Body text reads: a new client that speaks QWP over WebSocket straight from the page. No proxy service to write, deploy and keep in step with the schema. On the right, under 'straight from the page,' a diagram shows browser connecting to QuestDB with an arrow labelled QWP over WebSocket, captioned 'No Node modules. No polyfills. No proxy.' Under 'both ways,' three rows read: Write, row API, typed writers, batching, transactions. Read, streaming SELECT, bind params, cancellation. Survive, pooling, failover, replays unacked rows. A footnote chip reads Enterprise: follows the primary when a replica is promoted.

ALT QuestDB blog banner titled 'One table, three readers.' Body text reads: QuestDB SQL, Polars and DuckDB reading the same Parquet partitions, and agreeing. On the right, a glowing blue Parquet logo connects through a single point to three branching lines, each ending at a tile: the QuestDB logo, the Polars bear, and the DuckDB logo.

ALT QuestDB banner titled 'Governance, on one page.', tagged Docs · Governance. Body text reads: every governance feature, grouped by the question it answers. Map it straight onto your own policy or an auditor's checklist. On the right, under the heading 'grouped by the question it answers,' six numbered rows read: 01 Who may reach the data, and what can they do. 02 Who can do what right now. 03 Who read the data. 04 Where the data came from. 05 How long it is kept, and can it still change. 06 How to get it back. Below, two chips read Enterprise and Open source, followed by 'every item marked'.

ALT QuestDB Enterprise release banner. A huge white '4.1' fills the left of a dark midnight background, with a faint outlined '4.1' behind it on the right. Beneath it, in pink, reads 'Governance'. Along the bottom, three chips list the release highlights: Resource groups, Audited views, and Access control, with questdb.com/blog at the right. The top bar shows the QuestDB logo and an Enterprise v4.1 tag

ALT QuestDB release banner. A huge white '10.1' fills the left of a dark midnight background, with a faint outlined '10.1' behind it on the right. Beneath it, in pink, reads 'Fresher data'. Along the bottom, three chips list the release highlights: SUBSAMPLE, Exact percentiles, and sys.metrics, with questdb.com/blog at the right. The top bar shows the QuestDB logo and a Release v10.1.0 tag.



