Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Progress in performance and scalability with CockroachDB

cockroachlabs.com

Post reply on HN
Print view View original

21–30 of 47 posts

Re: Progress in performance and scalability with CockroachDB

#21

Post by mlevental »

anticensor wrote: post #4

Someone should create a fork with work-safe name. CockroachDB brings connotation of cockroaches, who are known by eating almost everything and living almost everywhere.

you know what's ironic? that in every thread there's one of you people complaining about the name - you're all just like cockroaches! no matter how successful cockroachdb becomes, no matter how technically impressive the product becomes, the naysayers never die.

can you imagine 20 years ago someone complaining that google wasn't safe for work because it had a silly name?

newsflash dummy: stop saying/thinking/repeating stupid things like this and it'll stop being the case that everyone is so conservative that silly names are inadmissible.

Re: Progress in performance and scalability with CockroachDB

#22

Post by eloff »

gigatexal wrote: post #2

I’m currently evaluating this as an alternative to vitess + percona mysql. But strict seralizability has its limitations.

What do you mean "strict seralizability has its limitations", you need something stricter? Or you have a need for something weaker for some reason?

Re: Progress in performance and scalability with CockroachDB

#23

Post by Confiks »

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?

Re: Progress in performance and scalability with CockroachDB

#24

Post by tshannon »

Confiks wrote: post #23

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?

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

#25

Post by orangechairs »

manigandham wrote: post #18
orangechairs wrote: post #16

Earlier quoted context omitted.

We released a managed version at the end of October, with auto-scaling, geo-replication, etc. --> https://www.cockroachlabs.com/product/managed/ Not sure that there any books on it yet.

The managed service doesn't autoscale, it's provisioned capacity by cores. We just did a call about it.

Our managed service is currently provisioned by cores. We automatically add nodes to your cluster based on your usage. You can also request to add more nodes if you anticipate spikes.

Re: Progress in performance and scalability with CockroachDB

#26

Post by accnumnplus1 »

mlevental wrote: post #21
anticensor wrote: post #4

Someone should create a fork with work-safe name. CockroachDB brings connotation of cockroaches, who are known by eating almost everything and living almost everywhere.

you know what's ironic? that in every thread there's one of you people complaining about the name - you're all just like cockroaches! no matter how successful cockroachdb becomes, no matter how technically impressive the product becomes, the naysayers never die. can you imagine 20 years ago someone complaining that google wasn't safe for work because it had a silly name? newsflash dummy: stop saying/thinking/repeatin…

There's also the irony in their name - anticensor.

Re: Progress in performance and scalability with CockroachDB

#27

Post by andreimatei1 »

Confiks wrote: post #23

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?

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

#28

Post by h1d »

mlevental wrote: post #21
anticensor wrote: post #4

Someone should create a fork with work-safe name. CockroachDB brings connotation of cockroaches, who are known by eating almost everything and living almost everywhere.

you know what's ironic? that in every thread there's one of you people complaining about the name - you're all just like cockroaches! no matter how successful cockroachdb becomes, no matter how technically impressive the product becomes, the naysayers never die. can you imagine 20 years ago someone complaining that google wasn't safe for work because it had a silly name? newsflash dummy: stop saying/thinking/repeatin…

That attitude does not fly with your boss.

Why limit the adoption for no good reason by choosing a weird name intentionally?

Re: Progress in performance and scalability with CockroachDB

#29

Post by manigandham »

Confiks wrote: post #23

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?

Sqlite would be my first recommendation, unless you need client/server access.

Re: Progress in performance and scalability with CockroachDB

#30

Post by qaq »

brod wrote: post #12

I've just released a small product using CockroachDB, in retrospect it was probably my favourite technical decision. Previously I'd used it as a toy and tested deployment strats but was skeptical (new tech and all that), but now that it's ticking along in the wild I'm very impressed across the board.

Are you using enterprise ? If not how are you handling backups?
Post reply on HN