Re:Progress in performance and scalability with CockroachDB
by Confiks on Wednesday November 28, 2018 @05:30PM
(#18556286)
I was wondering, quite unrelated to the article, if anyone knows if CockroachDB would be suited for small databases (and comparably modest computing/memory resources). I very much like its distributed properties, but only have a simple table of usernames and corresponding cryptographic material. Is CRDB easy to run and manage?
[ Parent
| on HN ]
Re:Progress in performance and scalability with CockroachDB
by andreimatei1 on Wednesday November 28, 2018 @05:59PM
(#18556493)
We have clients using CRDB in pretty constrained environments, and they use it primarily because of the easy administration. I think you'll find it easier to use than a MySQL or Postgres, for example.
Re:Progress in performance and scalability with CockroachDB
by tshannon on Wednesday November 28, 2018 @05:46PM
(#18556399)
I would expect your use case would be better suited by use just using postgres. However if you do need to scale to the point where you'd need to distribute your database and take advantage of CRDB's capabilities, it uses the Postgres protocol, so you most likely can just migrate your data and use the same code.
Re:Progress in performance and scalability with CockroachDB
by manigandham on Wednesday November 28, 2018 @06:16PM
(#18556602)
Sqlite would be my first recommendation, unless you need client/server access.
Re:Progress in performance and scalability with CockroachDB
by yellowapple on Wednesday November 28, 2018 @10:43PM
(#18557884)
I think the GP's stated need for replication would preclude SQLite unless one's willing to write one's own replication system.
Re:Progress in performance and scalability with CockroachDB
by manigandham on Wednesday November 28, 2018 @11:17PM
(#18558061)
Where's the stated need for replication?
Re:Progress in performance and scalability with CockroachDB
by yellowapple on Thursday November 29, 2018 @04:17AM
(#18559014)
"I very much like its distributed properties"