abyo-software/ferrodruid — explained in plain English
Analysis updated 2026-05-18
Replace a multi process Apache Druid cluster with a single lightweight binary for real time analytics.
Check a log of existing Druid queries against ferro-logcompat to see compatibility before migrating.
Run a real time OLAP database without needing Java, ZooKeeper, or a separate metadata store.
Deploy a Druid-compatible database through an AWS Marketplace AMI, container image, or Terraform module.
| abyo-software/ferrodruid | 04amanrajj/netwatch | 0xr10t/pulsefi | |
|---|---|---|---|
| Stars | 0 | 0 | 0 |
| Language | Rust | Rust | Rust |
| Setup difficulty | hard | moderate | hard |
| Complexity | 5/5 | 3/5 | 4/5 |
| Audience | developer | ops devops | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires building from Rust source with cargo, and cross-role mTLS needs certificates generated before the multi-binary cluster mode works.
FerroDruid is a database written in Rust that aims to work the same way as Apache Druid, a system used for storing and querying large amounts of time-stamped data in real time. The project is not made by or connected to the Apache Software Foundation. It is an independent rebuild of the public Druid data formats and network protocols, written from scratch. The main selling point is simplicity of deployment. A standard Druid setup needs six separate Java processes plus a coordination service and a separate metadata database. FerroDruid can run the whole system as one single compiled binary, with its own built in coordination using a library called openraft, so there is no Java runtime and no external coordination service to install. It can also run as six separate binaries, one per role, for larger setups that want the pieces split apart. The project includes a compatibility checker called ferro-logcompat, which reads a log of past Druid queries and reports which ones FerroDruid can already handle, which are partially supported, and which are not supported at all. It runs locally, does not touch your live Druid cluster, and does not send your query data anywhere. Supported features include the common SQL clauses such as SELECT, WHERE, GROUP BY, HAVING, ORDER BY, LIMIT and OFFSET, along with several Druid specific SQL time and string functions. It also implements all eight of Druid's native query types in single binary mode, with four of them working end to end when running as six separate role binaries. When roles talk to each other over the network, encrypted and verified connections are required by default. FerroDruid ships prebuilt images and deployment tools through AWS Marketplace, including an AMI, a container image, a Helm chart and a Terraform module. The license is BUSL-1.1, which restricts some commercial use rather than being fully open license, and the project documents known limitations and version by version compatibility results openly in its docs folder.
A Rust-native, single-binary reimplementation of Apache Druid, letting teams run a real-time analytics database without Java, ZooKeeper, or a separate coordination service.
Mainly Rust. The stack also includes Rust, SQL, Kafka.
Business Source License restricts some commercial and production uses rather than granting fully open permissions like MIT or Apache.
Setup difficulty is rated hard, with roughly 1h+ to a first successful run.
Mainly developer.
This repo across BitVibe Labs
double-check against the repo, no cap.