I took a spin a few weeks ago, it seemed like it would be a great fit to our needs: - we store alot of metrics for custom KPIs - we don't do joins - we don't

I took a spin a few weeks ago, it seemed like it would be a great fit to our needs: - we store alot of metrics for custom KPIs - we don't do joins - we don't need transactions - we're write once read heavy, sometimes re-write - crate's sharding, partitioning and replication, as well as "sql" api is great for our use case I even implemented some custom aggregation functions to check out the code, and it was easy. But what I liked the most was the responsiveness of the devs, the project seems to be moving at a good pace and the devs were very helpful over github. I wished the site made clear that it's using ElasticSearch under the hood, though. I don't know a thing about ES so I can't really comment on how the sharding, partitioning and replication are achieved. What I can remember from aphyr's blog (jepsen series) is that it's not recommended as a primary database though.