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

CockroachDB 19.2

cockroachlabs.com

Post reply on HN
Print view View original

21–30 of 63 posts

Re: CockroachDB 19.2

#21

Post by jseldess »

ralusek wrote: post #15

Some comments I have regarding the documentation. It seems like there is a lot describing how to set up a cluster and how to do various SQL operations that most people probably know how to do. I think the information that should be presented much more clearly are: 1.) How do we have to partition our data/what restrictions are in place? Basically, what considerations are necessary when designing the data model due to…

Head of Docs and Training at Cockroach Labs here. Thanks for this feedback, ralusek. It's spot on, and we're planning to create much more direct and prescriptive guidance and best practices for working with CockroachDB across multiple regions. That's when placement of data (via geo-partitioning or other approaches) is crucial for reducing network latency.

In case you haven't seen them, for now, we have docs on some data placement patterns for multi-region deployments: https://www.cockroachlabs.com/docs/stable/topology-patterns..... We believe the first and third are best for most cases. This tutorial also walks through the impact of using those patterns in a cluster spread across 3 regions of the US: https://www.cockroachlabs.com/docs/stable/demo-low-latency-m...

But we'll definitely continue working on better guidance here.

Re: CockroachDB 19.2

#24

Post by gigatexal »

Kognito wrote: post #9

Waiting for the comments about the name. On a more serious note, looking forward to trying this new release out. I found previous versions really straightforward to get up and running with on Kubernetes but performance was always lacklustre.

Try it out on your stack and with your data and see.

Re: CockroachDB 19.2

#25

Post by ainar-g »

a-robinson wrote: post #19
ainar-g wrote: post #17

Excuse me if that has been discussed numerous times, but I distinctly remember CockroachDB 2.0 coming out, and it being a big deal. Where are releases 3.0 to 19.0? Was the versioning scheme changed? How? Why? Other than that, I really wish I could use CockroachDB at "$COMPANY". Our architects, unfortunately, deem it “too new” and “unproven”. Bah.

They switched to calendar-based versioning earlier this year with the 19.1 release, for reasons explained in this blog post: https://www.cockroachlabs.com/blog/calendar-versioning/

Thanks for the link!

“““ We wanted to find a solution that would minimize frustration (and time-consuming meetings) internally, while setting the correct expectations with users around quality and stability. ”””

Honestly, this doesn't explain much. If anything, hearing “FooDB 19.1” makes me think of stuff like React 16 or Chrome 69. That is, of “hip dudes” who “live fast and bump major versions”. On the other hands, hearing “FooDB 2.16” would make me think “Yep, this thing seems stable as Perl or Linux”. The meetings point also doesn't explain anything. Go simply does a minor version bump every six months. Why couldn't Cockroach Labs just do that?

Oh well, who cares, really, as long as the product is great.

Re: CockroachDB 19.2

#26

Post by outside1234 »

gigatexal wrote: post #23
outside1234 wrote: post #18

Can we actually backup the database with the community edition yet? Last I checked this was impossible.

Backups are still an enterprise feature but doing a dump is still supported in the non paid version.

Yeah, that is not a real solution for a database of any real size, which is the only reason to use CockroachDB in the first place.

Re: CockroachDB 19.2

#28

Post by ainar-g »

Heh, they didn't seem to test their University website[1] before publising it. There is a gaping:

  
  Additionally, paste this code immediately after the opening  tag:
In the source code. That “” isn't escaped either, which makes the whole thing borked-up.

This is why we need XHTML.

[1] https://university.cockroachlabs.com/catalog

Re: CockroachDB 19.2

#29

Post by SEJeff »

fnordsensei wrote: post #13
ixtli wrote: post #10

Earlier quoted context omitted.

Those aren't nearly as resilient though. Now, if you made a version of sqlite that replicated itself inside your program then you could use botfly ...

The successor will have to be named TardigradeDB.

You can't even kill it with Boring Company's flamethrower! Tardigrades are virtually indestructible as going into space and coming back won't always kill them.

Re: CockroachDB 19.2

#30

Post by thatnerd »

ainar-g wrote: post #28

Heh, they didn't seem to test their University website[1] before publising it. There is a gaping: Additionally, paste this code immediately after the opening tag: In the source code. That “ ” isn't escaped either, which makes the whole thing borked-up. This is why we need XHTML. [1] https://university.cockroachlabs.com/catalog

Thank you, we didn't get that resolved beforehand. Should be fixed now.
Post reply on HN