This section describes the architecture of QuestDB, how it stores and queries data, and introduces features and capabilities unique to the system.

  • Designated timestamp is a core feature that enables time-oriented language capabilities and partitioning
  • type makes storing and retrieving repetitive strings efficient
  • Storage model describes how QuestDB stores records and partitions within tables
  • can be used for faster read access on specific columns
  • Partitions can be used for significant performance benefits on calculations and queries
  • allow performant time series analysis with a concise syntax
  • Root directory describes the directory contents of QuestDB for storage and configuration

Get started

This section explains how to install and run QuestDB using one of the following methods:

  • Docker for repeatable, portable and scalable installations
  • for direct downloads to run on Linux, macOS or Windows
  • Homebrew for running QuestDB on macOS

Once QuestDB is running, a guide is provided to .

  • Connect using Postgres or InfluxDB clients in a variety of languages
  • from popular languages using Postgres clients or InfluxDB line protocol, or in bulk via REST API
  • Query data using Postgres clients, REST API, or the Web Console
  • via an additional step before inserting records using InfluxDB line protocol

Guides

This section describes how to integrate QuestDB with third-party tools and utilities for collecting metrics and visualizing data:

  • instructions for connecting QuestDB as a datasource for building visualizations and dashboards
  • Kafka guide for ingesting data from topics into QuestDB by means of Kafka Connect
  • guide for collecting system metrics, specifying QuestDB as an output and visualizing the results

Operations

This section contains resources for managing QuestDB instances and has dedicated pages for the following topics:

  • for configuring server settings and system resources for common scenarios and edge cases
  • Data retention strategy to delete old data and save disk space
  • endpoint for determining the status of the instance

This section contains the reference documentation for the following categories:

APIs

Command-line options

The following resource provides info on options that may be passed to QuestDB when starting services:

Operators

Web console

QuestDB is bundled with a user interface which runs by default on port 9000. The following is reference documentation which describes how to use this UI:

  • reference for using the bundled UI

Support

We are happy to help with any question you may have, particularly to help you optimize the performance of your application. Feel free to reach out using the following channels: