DolphinDB

DolphinDB is a real-time analytics and stream-processing platform built around a high-performance time-series database. It is best suited to engineering and research teams that need several data models, high-throughput streaming and distributed deployment in one system. The main question is whether that breadth justifies operating a broader platform than a narrowly focused time-series database.

Overview

DolphinDB combines storage engines for time-series, OLAP and in-memory OLTP workloads. That makes it a plausible common data layer for organizations handling market, industrial, scientific or operational data with different latency and query requirements. Cloud, on-premise and hybrid deployment, plus horizontal cluster scaling, support both controlled infrastructure and expanding installations.

The trade-off is scope. Teams that only need a single-purpose time-series store may find its multiple engines, languages and integrations more platform than they need. For mixed workloads, however, consolidating these capabilities can avoid maintaining separate systems for every processing pattern.

Key features

More than 1,500 built-in analytical functions and more than 10 streaming engines give DolphinDB considerable range for real-time analysis. Batch and stream processing can use the same metric expression, a practical advantage when teams need consistent calculations across historical and live data rather than maintaining separate logic.

Programming support spans imperative, vectorized, functional and SQL paradigms. Queries can use DolphinDB SQL, ANSI SQL/SQL-92 or the DolphinDB scripting language, so teams can choose familiar SQL where appropriate while retaining specialized options for analytical work.

Ingestion covers text, binary, JSON, HDF5, Parquet, Arrow, ODBC, APIs, Kafka, MQTT, ZeroMQ, MySQL, MongoDB, HBase and kdb+. This is useful for a heterogeneous pipeline, especially when existing systems cannot be replaced. Kafka publishing and subscription support JSON, DolphinDB and string formats; on ARM Linux, SASL authentication and zstd compatibility are unavailable, which matters for deployments relying on those Kafka features.

The distributed system supports horizontal scaling, load balancing, fault tolerance, distributed transactions and high availability across data nodes, controllers, streaming components and API clients. Security controls include user and group access management, multiple privilege types, function views, RSA encryption and HTTPS. The DolphinDB VS Code extension supports script execution, completion, multi-user connections, version control and debugging, while the Python API documents Windows amd64, Linux x86_64 and aarch64, and Mac x86_64 and arm64 environments.

Enterprise components extend the platform for particular jobs: Swordfish embeds DolphinDB, Shark provides a GPU version, Starfish targets quantitative research workflows and Octopus handles complex event processing. These options are most relevant to specialized enterprise teams rather than small deployments.

Pricing

DolphinDB Community Edition — free, perpetual license. It supports up to two nodes, with two CPU cores and 8 GB of RAM per node. That is a genuinely useful zero-cost environment for evaluation, small services and development, but the node and hardware ceiling rules out using it as a free path to a larger production cluster.

DolphinDB Enterprise Trial — free. It supports high-availability clusters and includes expert technical support. This is the more appropriate choice for evaluating resilient, multi-node architecture or for teams that need direct technical assistance during assessment.

Platforms

DolphinDB supports API, extension, Linux, self-hosted, web and Windows environments. Deployment can be cloud, on-premise or hybrid. SQL support, retention policies and horizontal scaling are provided, with integrations spanning databases, message systems, file formats and APIs. The documented Python API also covers Mac architectures in addition to Windows and Linux.

Who it's for

DolphinDB is aimed at organizations in finance, energy, power, transportation, industrial manufacturing and scientific research. It fits teams combining time-series analysis, OLAP, in-memory transactions and streaming in distributed systems, particularly when consistent batch and live metrics matter. Quantitative researchers may benefit from Starfish, GPU-oriented workloads from Shark, and complex event processing from Octopus.

It is less compelling for a small project that needs only a straightforward time-series database, or for anyone whose intended installation exceeds the Community Edition’s two-node, per-node resource limits without an Enterprise budget.

Pros and cons

Pros

Multiple engines cover time-series, OLAP and in-memory OLTP workloads in one platform.

More than 1,500 analytical functions and over 10 streaming engines support demanding real-time use cases.

Shared metric expressions for batch and streaming can reduce duplicated analytical logic.

Distributed transactions, fault tolerance and high availability address serious clustered deployments.

Broad ingestion, language and deployment support accommodates heterogeneous data estates.

A perpetual Community Edition and a no-cost Enterprise Trial lower the barrier to evaluation.

Cons

The Community Edition is limited to two nodes and two CPU cores with 8 GB RAM per node.

The platform’s breadth brings more operational and architectural scope than a focused time-series database.

Kafka on ARM Linux lacks SASL authentication and zstd compatibility.

Enterprise production pricing is custom, so long-term cost cannot be determined from the published plans.

Alternatives

Choose InfluxDB when a freemium time-series product with a single-node Core option or usage-based Cloud Serverless plan better matches your deployment. QuestDB is a strong alternative for an Apache 2.0, self-managed single instance with community support. Pick VictoriaMetrics when open-source single-node or cluster editions are the priority. TDengine suits readers seeking an AGPL open-source TSDB with clustering capabilities. Warp 10 offers a free sandbox for trying its platform. CnosDB provides an AGPL-3.0 community protocol and enterprise option. LinDB is an Apache 2.0 open-source choice without a free trial. Choose OneTick when a paid, requirements-based offering is acceptable. For broader category comparisons, see Time-Series Databases, Multimodel Databases and OLAP Software.

Verdict

DolphinDB is a strong choice for data-intensive organizations that need time-series, analytical and streaming workloads with distributed scaling and several programming models in one platform. Its main reason to choose it is the combination of breadth and serious cluster capabilities, with free editions for both constrained use and high-availability evaluation. Look elsewhere if you want a simpler specialist database, require ARM Linux Kafka security features, or need predictable published Enterprise pricing.