QWP: QuestDB's own binary wire protocol for ingestion and queries

QuestDB 10.0 introduces the QuestDB Wire Protocol (QWP), a binary, columnar, bidirectional protocol designed to improve ingestion and query-result performance while unifying reads, writes, and DDL through a single client and connection string. QWP is reported to ingest up to 19 million rows per second and stream results at 220 million rows per second by avoiding text serialization and row-by-row processing, while supporting Apache Arrow, pandas, Polars, and other dataframe-oriented workflows in supported clients. Migration from Java ILP ingestion generally requires only changing the connection string from HTTP to WebSocket, although QWP uses asynchronous error handling and different flushing behavior. The protocol also provides multi-host routing, primary and replica targeting, health-aware failover, and store-and-forward buffering that can persist queued writes to disk during outages, with at-least-once replay requiring deduplication keys to prevent duplicates. ILP, PGWire, and the REST API remain supported for existing InfluxDB, PostgreSQL, BI, scripting, and third-party tool integrations, while QWP is recommended for new applications using official QuestDB clients; open-source deployments include client-side resilience features, whereas Enterprise adds replication and primary-replica failover capabilities.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.