QuestDB@QuestDb
Nov 6
New in the #QuestDB third-party integrations: adbcBridge, ADBC drivers for QuestDB.

Our Arrow-over-QWP clients are C/C++, Rust, Python and Ruby. In C#, Java, Go or TypeScript, or on a QuestDB older than 10, the bridge gets you there.

questdb.com/docs/integrati…
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.
0
0
3
194
QuestDB@QuestDb
Nov 5
Several teams sharing one #QuestDB? Since Enterprise 4.1 a user only sees the objects it has a permission on.

Pairs well with resource groups for shared clusters.

questdb.com/docs/security/…
QuestDB Enterprise 4.1 banner titled 'Object visibility, per principal.', tagged Access control, with a pill reading tables(), SHOW TABLES, pg_catalog. Body text reads: a principal only sees the objects it holds a permission on. Everything else is simply not there, information_schema included.
1
0
4
211
QuestDB@QuestDb
Nov 4
How fast can you replay a full trading day of US equities? New on the #QuestDB blog: 353,657,441 rows of top of book, in strict order, to a Python client in 129s at 2.74M rows/s.

Across 8 connections: 32.5s, at the network link's limit.

questdb.com/blog/questdb-m…
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.
0
0
1
98
QuestDB retweeted
Jeremy Morgan
@JeremyCMorgan
Nov 4
Oliver Parkinson parses iRacing .ibt files in Go with zero-copy mmap reads: about 31M ticks a second on an M4 Pro, then stores them in QuestDB on a Raspberry Pi 5. Self-hosted telemetry, MIT licensed.

github.com/OJPARKINSON/Te…
1
1
2
345
QuestDB@QuestDb
Nov 3
There is now a Ruby client for #QuestDB, published as a gem.

QWP over WebSocket, ingest rows, columns or Arrow, and queries that come back as Enumerable or straight into Polars. Blocks release their leases for you, and I/O runs without the GVL.

questdb.com/docs/connect/c…
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
2
0
1
94
QuestDB@QuestDb
Oct 30
New #QuestDB client, and this one runs in the browser: QWP over WebSocket straight from the page, no backend service in between.

Writes with batching and transactions, streaming SELECT results, and values as real JS types rather than JSON.

questdb.com/docs/connect/c…
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.
2
0
2
195
QuestDB@QuestDb
Oct 29
New on our blog: one table, three readers. #QuestDB stores older partitions as Parquet, SQL spans native and Parquet in one query, and Polars and DuckDB read the same files directly.

Counts, volumes and highs match. VWAP agrees to 12 significant digits.

questdb.com/blog/questdb-p…
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.
7
0
7
190
QuestDB@QuestDb
Oct 28
New in the #QuestDB docs: a governance and auditing guide. Every governance feature on one page, grouped by the question it answers, from access control and entitlement review to read auditing, lineage, retention and recovery.

questdb.com/docs/security/…
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'.
0
0
3
145
QuestDB@QuestDb
Oct 27
We just shipped #QuestDB Enterprise 4.1.0.

- Resource groups: concurrency, CPU and memory limits per team
- Audited views, every read recorded with its parameters
- Users only see objects they have permission on
- OIDC for services and managed identities
- Built on QuestDB 10.1
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
3
0
4
171
QuestDB@QuestDb
Oct 27
Replying to @QuestDb
Read the full post at questdb.com/blog/questdb-e…
0
0
1
52
QuestDB@QuestDb
Oct 23
We just shipped #QuestDB 10.1.0.

- Merge-append partitions: late writes no longer rewrite the whole partition
- SUBSAMPLE, find your most significant rows
- Exact percentiles
- Metrics history in sys.metrics
- Parallel GROUP BY over joins
- Faster LATEST ON and symbol filters
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.
1
0
2
134
QuestDB@QuestDb
Oct 23
Replying to @QuestDb
Read the full story at questdb.com/blog/questdb-1…
0
0
1
60
QuestDB@QuestDb
Oct 22
New on our blog: live Databento market data into #QuestDB Enterprise, end to end. A TOML config file for ingestion, order book analytics in SQL, a Web Console dashboard, and history ageing into Parquet in cold storage.

20,000 to 65,000 book updates a second at the open.🧵
QuestDB blog banner. A wide dark chart panel fills the top half, showing dense cyan volume bars with a glowing pink line running across them, both spiking sharply near the left edge. Below, a tag reads Market Data, followed by the title 'Ingesting live market data from Databento into QuestDB'.
1
1
3
135
QuestDB@QuestDb
Oct 22
Replying to @QuestDb
Read more at questdb.com/blog/ingest-da…
0
0
0
41
QuestDB@QuestDb
Oct 21
Version 0.25 of the #QuestDB Kafka connector is out. No config changes needed.

High cardinality tasks no longer hit a ceiling past a couple of million distinct symbols, idle connections can be kept alive with keepalive_interval_millis, and offset commits are quicker.
QuestDB banner titled 'Kafka connector, version 0.25.', tagged v0.25 · Kafka connector, with a pill reading 0.25, http::, ws::, tcp:: keep working. Body text reads: nothing changes in your configuration. The improvements come from client 1.3.10 and apply when you connect over QWP. On the right, under the heading 'keep idle connections alive,' a code card shows client.conf.string with keepalive_interval_millis set inside it. Below, under 'also over QWP,' three rows read: no symbol ceiling, past one or two million distinct values; quicker commits, flush stops waiting out the ack timeout; and clearer errors, missing or blank config caught up front. A footnote reads: keepalive is off by default. Pings stop idle timeouts dropping quiet links.
0
0
0
78
QuestDB@QuestDb
Oct 20
One of the SQL extensions you only find in #QuestDB: exchange calendars.

Put a MIC code in the time filter and the query sees only real trading sessions. Weekends, holidays, early closes and daylight saving shifts are already in the schedule.

questdb.com/docs/query/ope…
QuestDB Enterprise banner titled 'Trading hours, in the filter.', tagged Enterprise · Exchange calendars, with a pill reading #XNYS, a MIC code, not a holiday list. Body text reads: no holiday list, no session window, no timezone math. A MIC code in the time filter, and daylight saving comes for free. On the right, under the heading 'january on the nyse, sessions only,' a code card shows: WHERE ts IN '[2026-01]#XNYS'. Below, under 'one filter, any market,' three rows read: XNYS, no weekends, no holidays, real early closes; XHKG, both sessions, lunch break taken out; and your own, custom sessions, overrides, internal codes. A footnote reads: NYSE, 14:30 to 21:00 UTC in winter, 13:30 to 20:00 in summer. Same filter.
0
0
0
81
QuestDB@QuestDb
Oct 19
Still running #QuestDB on ZFS to compress your tables? You can drop that layer.

Partitions convert to Parquet, compressed in the format itself, so compression happens inside the database rather than under it. And they stay fully queryable.
QuestDB banner titled 'Compression, without ZFS.', tagged Storage · Parquet, with a pill reading Parquet partitions, open source and Enterprise. Body text reads: Parquet partitions are compressed in the format itself and stay fully queryable. On Enterprise, storage policies convert them by age. On the right, under the heading 'where compression happens,' two stacks compare before and now. Before shows three layers: QuestDB table in native format, ZFS compression struck through as a filesystem layer, and disk. Now shows a pink QuestDB table box labeled Parquet partitions, compressed, sitting directly on disk. Below, a panel headed 'codec, set in server.conf' lists LZ4_RAW as the default, plus zstd, gzip, snappy and brotli. A footnote reads: ALTER TABLE converts existing partitions you point it at.
0
0
1
111
QuestDB@QuestDb
Oct 16
Applications should not log into your database as a person.

In #QuestDB Enterprise a service account cannot belong to any group, so every permission it holds was granted explicitly. And you can ASSUME one to check exactly what it can do before shipping.
QuestDB Enterprise banner titled 'Service accounts, not your login.', tagged Enterprise · Service accounts, with a pill reading no groups, nothing inherited. Body text reads: a principal for an application, not a person. Every permission it holds was granted to it explicitly, so the grants are the blast radius. On the right, under the heading 'one table, one protocol, nothing else,' a code card shows: CREATE SERVICE ACCOUNT ingest_app WITH PASSWORD 'pwd'; GRANT HTTP TO ingest_app; GRANT INSERT ON sensor_data TO ingest_app; ALTER SERVICE ACCOUNT ingest_app CREATE TOKEN TYPE JWK; Below, under 'memory limits too,' a card reads: SET MEMORY LIMIT 1G, per account, not inherited. A footnote reads: no personal login in the pipeline.
0
0
0
100
QuestDB@QuestDb
Oct 15
The #QuestDB Enterprise Kubernetes Operator docs are now live: EKS and AKS, migration, runbook, backup and restore, HA, API reference, known limitations.

The operator holds no cloud identity and does no object store I/O at all. The database pods do all of it. 🧵
QuestDB Enterprise banner titled 'Kubernetes operator, fully documented.', tagged Enterprise · Kubernetes, with a pill reading EKS + AKS, docs complete. Body text reads: from installation to the support matrix, everything you need to run QuestDB Enterprise on Kubernetes. On the right, under the heading 'what the docs cover,' ten chips read: installation; getting started on EKS and AKS; migrating an instance; configuration; operator runbook; backup and restore; high availability; troubleshooting; API reference; and limits and support matrix. Below, a panel headed 'no cloud identity, no object store I/O' shows two lanes: operator, with a crossed-out line to your bucket, and db pods, with a green arrow reaching your bucket. A footnote reads: EKS with IRSA, no static Secret at all."
1
0
0
87
QuestDB@QuestDb
Oct 15
Replying to @QuestDb
Read more at questdb.com/docs/enterpris…
0
0
0
37
Load more