4 ms·

Thanks! Did you consider any other options?

• manigandham 8y ago
  What scenario are you looking for? TiDB is another competitor but mysql dialect and still early, missing lots of features. For pure data-warehousing, we used MemSQL which is incredibly fast but can be expensive. SQL Server is a great all around database if you want in-memory tables, columnstores, native graph queries, full-text search, and very high performance and can live with a single-node design (with optional HA cluster).
  • hemancuso 8y ago
    Mostly an easy and performant HA story that can scale to a huge number of queries per second for an app that is largely CRUD and vanilla webapp saas queries. Cockroach seems perfect but the performance seems pretty scary in certain scenarios. Being able to just drop the DB into a k8s cluster and not worry too much about failover gotchas and leader election has a lot of value. As does being able to throw more nodes on for more performance. Complicated OLAP queries aren't in scope.
    • manigandham 8y ago
      Either are a good fit for you, but since you have simpler queries than CRDB will be easier to run. Performance is fine, why do you say it's scary? OLAP will just be slow, but it's also distributed and unoptimized. Highly concurrent OLTP can't really get slow unless you're trying to stretch the cluster over multiple geo regions.