12 Questions Answered on Building a Time-Series Database with KairosDB
Blog post from ScyllaDB
In a recent webinar featuring Brian Hawkins, the creator of KairosDB, various questions about building a time-series database using KairosDB and ScyllaDB were addressed. It is possible to use a single node of each for development, but for production, multiple nodes of both are recommended to ensure high availability and resiliency. KairosDB requires Java 1.8 or higher and certain server specifications, while ScyllaDB suggests a minimum of 4 CPUs, 8GB RAM, and 1TB SSD for optimal performance. The combined solution of KairosDB and ScyllaDB offers advantages over ElasticSearch, including easier administration, maintenance, and better throughput and latency, with the added capability of setting TTL for data. The webinar also discussed the ability to configure KairosDB for high availability and scalability, the lack of special time-series support in ScyllaDB but its efficient handling of wide rows, and potential latencies when reading data across nodes. While a direct pass to backend storage is being developed for KairosDB, the current setup effectively queues data, and discussions continue on the KairosDB mailing list for further updates.