Home / Companies / QuestDB / Blog / Post Details
Content Deep Dive

QuestDB 2025: Year in Review

Blog post from QuestDB

Post Details
Company
Date Published
Author
Javier Ramirez
Word Count
2,538
Company Posts That Month
23
Language
English
Hacker News Points
-
Post removed?
No
Summary

In 2025, QuestDB underwent significant enhancements across 16 open-source and 15 enterprise releases, focusing predominantly on capital markets while also gaining traction in other sectors like energy, aerospace, and fintech. Key developments included advanced data types such as arrays for order book analysis, nanosecond precision timestamps for high-frequency trading, and DECIMAL for exact financial computations, which are crucial for sectors requiring high precision like crypto. The introduction of ASOF JOINs and optimized JOINs, including RIGHT and FULL OUTER JOINs, improved temporal query performance for trading workflows. Materialized views were enhanced to manage vast amounts of market data efficiently, while symbol auto-scaling and various query optimizations addressed high-cardinality challenges. The year also saw a focus on open formats with Parquet support, enabling seamless data interoperability without duplication, and the introduction of enterprise-level features like OAuth2/OIDC authentication and robust replication across storage mediums, ensuring high availability and security for financial institutions. Looking forward to 2026, QuestDB plans to enhance integration capabilities further with features like window JOINs, SQL views, and LLM-assisted analytics, continuing its mission to meet the demands of quantitative finance and beyond.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
Real-time 4 7,285 1,202 224 +60%
Data Pipeline 2 896 273 69 +167%
LLM 2 3,775 638 202 -32%
Observability 2 2,671 527 151 +5%
Use This Data

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.