iAccount based inUnited Kingdom
About this account
- Account based in
- United Kingdom
- Connected via
- Web
Account-level information from X, not a live location or the device used for a specific post.
QuestDB (YC S20) is the fastest open source time series database. https://nitter.cf/t.co/g0aLl6RpwB
- Tweets2.5K
- Following266
- Followers2.3K
- Likes750
ALT QuestDB Enterprise banner titled 'Enterprise, 30 days, your workload.', tagged Free trial · Enterprise, with a pill reading latest build, no limits on cores or nodes. Body text reads: no discovery call, no demo. Request the trial and get the download link within one business day. The URL questdb.com/enterprise/trial sits below. On the right, under the heading 'try it for real,' five checked cards read: Ingest, your own data shape and rates; Tiered queries, hot storage plus Parquet on S3, GCS, Azure, NFS; Incremental backups; Roles and grants, with SSO and TLS in front; Take a node down, replication and restart-free promotion.
ALT QuestDB banner titled 'Five joins, built on time.', tagged Guide · Time series joins. A pill shows two timestamps, 14:54:42.340 and 14:54:42.323, with a not-equal sign between them, labeled '= returns nothing'. Body text reads: equality joins fall apart for time. Choose by starting from the row you want back. On the right, under the heading 'the row you want back,' five cards pair each join with its use: ASOF JOIN, the state of another series at each event; WINDOW JOIN, a summary of what it was doing nearby; HORIZON JOIN, the value at fixed offsets around it; LT JOIN, the previous bar, no look-ahead bias; SPLICE JOIN, every change on two feeds, neither in charge
ALT QuestDB Enterprise banner titled 'Row level access control.', tagged Enterprise · Row level access, with a pill reading GRANT SELECT, on the view, not the table. Body text reads: one table, many desks, and each desk sees only its own trades. Put the filter in a view and grant SELECT on the view. Three chips below read user, group and service account. On the right, under the heading 'one master, a thin view per desk,' a layered diagram: a dashed card for the trades base table marked 'never granted', below it a blue card for trades_master, described as columns and logic with an overridable filter, also marked 'never granted', and fanning down from it three pink cards, trades_fx, trades_rates and trades_equities, each marked 'granted' in green. Two footnotes read: each desk view pins the filter to a fixed value, and change the master once, every desk picks it up.
ALT "QuestDB banner titled 'Kafka connector, now on QWP.', tagged 0.24+ · Kafka connector, with a pill showing http:: struck through and replaced by ws::, labeled 'three lines of config'. Body text reads: Kafka offsets commit only once QuestDB has confirmed the rows. Anything unconfirmed stays uncommitted and gets retried. On the right, under the heading 'confirmed, then committed,' two ordered lanes show rows confirmed by QuestDB in green, then offsets committed to Kafka in pink, footnoted 'unconfirmed rows are retried, not lost.' Below, two rows read Backpressure, pauses consumption instead of buffering, and Follows the primary, list every node in addr, Enterprise. A closing line reads: dedup on the table and retries stop producing duplicates."
ALT QuestDB banner titled 'Resource groups, coming to Enterprise.', tagged Coming soon · Enterprise. Body text reads: one instance, many kinds of query. A named policy decides how much of the box each kind gets. On the right, under the heading 'one policy, three controls,' three rows each show a partially filled bar: Concurrency, queries at once; CPU share, while groups compete; and Memory, held between them. Below, a panel headed 'attached to', noted 'follows the asker, not the query', holds three chips reading user, ACL group and service account. A footnote reads: setup will be two statements, create the policy, map a principal.
ALT QuestDB banner titled 'One statement, whole schema.', tagged Cookbook · Copy schema, with a pill reading SHOW CREATE DATABASE, data free. Body text reads: one round-trippable DDL statement per row, in dependency order. Replay it on an empty instance and the structure is there. On the right, a terminal card shows the statement SHOW CREATE DATABASE; below it, a diagram of two instances side by side. The live instance lists trades, quotes, trades_1m as a materialized view, and grants as ACL, footed 'years of rows'; an arrow between them is labeled DDL above and 'no data' below; the empty instance lists the same four objects in pink, footed '0 rows'. Two chips read INCLUDE (SCHEMA) and INCLUDE (ACL), marked 'one side only', with a footnote: over REST, into a .sql file, or straight to the target.