Graphite vs KairosDB: What are the differences?

1. Query Language: Graphite uses a simple query language that allows users to query metrics based on patterns and wildcards, while KairosDB provides more flexibility with a more powerful query language that supports various functions such as aggregations, transformations, and filtering based on tags.

2. Aggregation Functions: Graphite offers basic aggregation functions like sum, average, min, and max, whereas KairosDB provides a wide range of advanced aggregation functions such as percentile, group by time, moving average, and rate interpolation.

3. Data Retention: Graphite does not come with built-in data retention policies, so users have to manage data retention manually, whereas KairosDB includes configurable data retention policies that allow users to define how long data should be stored before it is automatically purged.

4. High Availability: Graphite does not natively support high availability or clustering, requiring users to implement their own solutions for redundancy and failover, while KairosDB offers built-in support for high availability and clustering through a distributed architecture that ensures data reliability and fault tolerance.

5. Data Model: Graphite follows a simpler data model with hierarchical organization using dots for separating components in metric names, while KairosDB utilizes tags to provide a more flexible and scalable data model that allows for easier data exploration and filtering based on metadata.

6. Community Support: Graphite has a larger community and more extensive documentation, making it easier for users to find resources, troubleshoot issues, and collaborate with other users, whereas KairosDB has a smaller but still active community, which can make finding help and resources more challenging at times.

In Summary, Graphite and KairosDB differ in query language flexibility, aggregation functions, data retention policies, high availability support, data model complexity, and community support.