2021 has been a great start for us at QuestDB, and we'd like to share our highlights so far. We've had some exciting additional functionality added based on community feedback, and there are quite a few fixes that enhance the stability of the system.
We hope you enjoy reading about these features and catching up on the latest content from recent weeks to get the most out of QuestDB.
release version 5.0.6
contains highlights such as a complete refactoring of PostgreSQL wire support,
including binary support. RFC339Nano timestamp support enables alerting via
Grafana, a new
build() function which provides version number and commit hash
for troubleshooting, and
CREATE TABLE IF NOT EXISTS SQL support.
Fixes have landed on PostgreSQL wire using popular Rust, Python, Go libraries, concurrent CSV imports, preventing data corruption when disk space is full, and multiple SQL fixes.
This is a brief summary of our highlights, so the full list of changes and the supplementary documentation for new features can be found in the 5.0.6 Release Notes page on GitHub.
We hosted a webinar on Thursday 21st January, with presentations from Toggle, DATRON, Ably, FORRS, and Chainslayer. They share feedback about their experience with QuestDB to solve problems in various domains and how it compares to InfluxDB, and we had a broader discussion about what's on the roadmap for QuestDB. The webinar is available to watch back on YouTube.
As a bonus from this event, Marc Recht from FORRS shared his Jupyter notebook, which contains interactive queries and plots based on financial data stored QuestDB using Python. Marc's notebook is available to view on GitHub .
We have the following editorials to share where we're happy to be featured in the following outlets:
- Python weekly featured our application monitoring tutorial
- VentureBeat featured QuestDB on the rise of time-series databases
- StackShare listed QuestDB in the top 50 new developer tools of 2020
- Analytics India adds us to the most prominent time-series databases
- OSChina featured QuestDB following the Best Open Source Software 2020 award by Infoworld
We’re building a new Community page on questdb.io, which helps contributors with suggestions for getting involved and offers some must-have swag for the fantastic interaction as a way for us to give back. For a quick summary of what the last month looked like, here's a small overview of January in numbers :
- 200+ new stargazers on the QuestDB repository on GitHub
- 80+ new developers joined our community on Slack with;
- 3,700+ messages in our Slack workspace
We had great discussions with the community on the benefits of adding Kafka to software stacks in front of QuestDB, how to get Postgres wire running using different languages, and plenty of talk on the latest changes landing on QuestDB.
There is a new enterprise page for users ready to take their production deployments to the next level. If product training, support, deployment management, authentication, and access control is a must, we're ready to assist in making sure critical systems stay running.
Our new Tutorials page contains outstanding community contributions using several technologies, languages, and software stacks that use QuestDB in various applications. One of the highlights is our partnership with OSS project n8n.io who provides a low-code workflow automation platform. We published a tutorial for this integration that demonstrates how to build a low-code bitcoin ticker with QuestDB.
Some of our top picks and featured tutorials are:
- Monitoring the uptime of an application using Python, Nuxt.js
- SQL extensions for time series in QuestDB
- Building a monitoring dashboard with Grafana
We've added documentation about strategies for data retention using QuestDB. Tables can be partitioned by date, and stale partitions can be dropped when the data is no longer needed or to adhere to data retention policies. Details on how to partition data in this way and drop stale partitions can be found on our Data Retention page.
Telegraf is a client for collecting metrics from many inputs and supports sending these metrics to various outputs. QuestDB's support for ingesting influx line protocol messages means it's simple to directly receive metrics from many sources to a QuestDB instance using this agent. Details of sending metrics from Telegraf to QuestDB over TCP and UDP can be found on the Telegraf client page.
We're excited to see our users and the community grow, and we want to say thanks for being a part of the journey! If you’ve any questions about this update, reach out to us and say hi on Slack or Stack Overflow.