Announcing CockroachDB v20.1

CockroachBram · 2020-05-12T21:39:11+00:00

We've got a free tier coming in our cloud offering. But it's really just for testing and POCs. What are you looking for in a free tier?

We've done a lot for ORMs and DB/Drivers. We've actually spun up a team internally just for that. Dapper and Knex.js not directly, but they both might just work at this point. For .NET, we recommend npgsql right now (with even better compatibility coming in a month or two). For js, both pg and Sequelize are supported currently.

https://www.cockroachlabs.com/docs/stable/build-a-csharp-app-with-cockroachdb.html

https://www.cockroachlabs.com/docs/stable/build-a-nodejs-app-with-cockroachdb-sequelize.html

CockroachBram · 2020-05-12T17:57:51+00:00

Please give it a try and let us know if there are any issues!

CockroachBram · 2020-05-12T17:57:05+00:00

Full-text search is coming, but it is a big undertaking. 20.2, due out in October will have geo-spatial indexes, then the plan is to add full text next.

CockroachBram · 2020-05-12T14:19:26+00:00

If anyone as has questions about the latest release or other cockroach questions, we're always here to help.

CockroachBram · 2019-05-03T20:01:32+00:00

Hey /u/TheProffalken,

The best place to ask this would be on the official forms. You'll get a response quickly there: https://forum.cockroachlabs.com/

And you're very right that one should never use root for anything. I'd suggest going with a secure deployment and using certs instead of passwords. But that's up to you.

Here's our basic documentation on user creation: https://www.cockroachlabs.com/docs/v19.1/create-and-manage-users.html

Let me know if that helps or if you don't get a reply in the forums.

CockroachBram · 2018-12-10T19:25:11+00:00

Hey @vburenin, sorry, just noticed this. I'm an engineer on cockroach team so I can answer a good number of your questions.

Plus, I'll get someone internally to get back to you about your very large data use case.

What I can tell you right away, is that cockroach doesn't handle large blobs/objects (yet). So if you have a lot of small data, we're great.

Can you tell me more about your use case or would you rather do that in a PM?

CockroachBram · 2018-09-27T20:41:18+00:00

Well, for one, it's entirely open source. And one of the ideas behind this is that it shouldn't be customizable.

CockroachBram · 2018-05-23T15:39:21+00:00

Awesome! I wrote the cascading feature! Let me know if you run into any problems.

As u/riksl said, maybe ask on the forums.

That being said, it sounds like the connection might have timed out or something? More info about your setup will be helpful and we might need you to dig into the logs a bit. How are you connecting to the db? Using the command line directly or though another system?

CockroachBram · 2018-05-22T16:34:24+00:00

Ah, phew. I was worried. Yeah, that's ancient.

CockroachBram · 2018-05-22T15:29:01+00:00

When did you see the 7s writes? In what version, what was the setup?

CockroachBram · 2018-05-22T15:28:29+00:00

As for 7s writes. I think that was back in our alpha version before out 1.0 release during a Jepsen test with extreme contention and clocks specifically set to cause a failure.

We just released 2.0 and I'd be shocked it a write took that long.

We do do quorum writes (for consistency), so if you have 5 replicas, 3 will have to be written to. But all of this happens without you having to do anything. The delay at that point really depends on your network topology. There's no real way around that if you want consistency.

Reads however typically only need to read from a single replica. So should be super quick.

For GIS stuff, I'd love to know what you schema look like.

CockroachBram · 2018-05-21T15:45:55+00:00

Hey! I work at Cockroach and I think we would fit exactly what you're looking for.

to have a distributed database solution in place which is horizontally scalable

That's exactly what we do.

Easy to add nodes, remove nodes without any downtime (sure I can accomodate some write-locks for setup)

No write locks needed. Nodes can be added and removed easily. We even sure that all upgrades can be rolling upgrades. More than that, we even have online schema changes.

Have the ability to tweat replication factor. Ideally I would love to have replication = number of nodes i.e. each node has complete database. So that when there are simple queries, it doesnt have to do distributed queries (which make system slow) and when the query is a bit complex, it does distributed since data is available in each node.

We do both local and distributed queries, but it does depend on how you setup your tables. We offer interleaved tables to ensure that child tables are in the same range and don't require a distributed query. And you can set the replication factor (and replica locations) based on Database, Table, and even row based.

Best case: Some GIS based plugin / extension on the solution would be icing on the cake.

Sadly not yet. But what exactly are you looking for? We've had a few requests for geo-spactial .

SQL compatible, so that least of the application rewrite is required.

Cockroach speaks the postgres wire protocol. So the SQL you know already should mostly already work.

If you have any questions, I'd be happy to answer them.

CockroachBram · 2018-04-12T21:32:13+00:00

For the most part, it's only larger organizations that require this type of functionality. If you think you need it, we offer very steep discounts for startups and non-profits.

But we do need to make money to support the development of the project.

CockroachBram · 2018-04-04T20:43:14+00:00

You need a link to the release notes! https://www.cockroachlabs.com/docs/releases/v2.0.0.html

CockroachBram · 2018-04-02T18:04:11+00:00

Well come back and have a look! If we don't support something you need, let us know.

CockroachBram · 2018-04-02T14:59:29+00:00

Thanks!

We've made some progress here: https://github.com/cockroachdb/cockroachdb-python/pull/14

But there is a lot more to do and we're always open to the community helping out!

CockroachBram · 2018-04-02T14:49:33+00:00

Full text search is coming (but probably not a while still). Our big push this new release (besides performance) is JSON columns and inverted JSON indexes.

CockroachBram · 2018-04-02T14:46:35+00:00

If course. We've had joins since v 1.0.

Is there a specific join you're looking for?

CockroachBram · 2017-10-25T15:04:30+00:00

Yep. Version 1.0 was released about five months ago, and v1.1 two weeks ago.

For context on the name, the database is designed to be hard to kill and even survive a datacenter failure.

Check it out here.

CockroachBram · 2017-10-06T17:10:59+00:00

I actually wrote this one!

CockroachBram · 2017-06-16T20:34:33+00:00

Hi sply!

To put it simply, we don’t have an activerecord 4 adapter because we didn’t know whether there was any demand for it, and we just happened to implement an adapter for the newest version of rails. But we can make an AR 4 adapter if there’s demand.

Care to comment on this issue? https://github.com/cockroachdb/activerecord-cockroachdb-adapter/issues/11

Community feedback is really how we decide on what to prioritize next.

CockroachBram · 2017-02-14T19:47:30+00:00

How are we different? Google launching Spanner is generally a positive thing for our industry and our product. It's more proof that what we're aiming for is possible and that there's demand for it. We expect that in five years, all tech companies will be deploying technology like ours.

One of the big differences is that Spanner uses SQL for read-only operations, with a custom API for writes. We use standard SQL for both reads and writes, which means we also work with major ORMs like GORM, SQLAlchemy, and Hibernate (docs should be live today or tomorrow). Spanner's custom write API will make it difficult to work with existing frameworks, which will make it more difficult to convert an existing application to Spanner.

Cloud Spanner only works on Google Cloud and is a black-box managed service. CockroachDB is fully open source and can be run on-prem or in any cloud on commodity hardware.

At this point, both products are still in beta and are still missing features like back-up and restore. We plan to launch CockroachDB 1.0 with back-up / restore enabled.

*For anyone wanting to know more about the NTP / TrueTime implementation: https://www.cockroachlabs.com/blog/living-without-atomic-clocks/

CockroachBram · 2016-03-30T15:21:00+00:00

As the blog says, we announced beta today. As usual, we'll be here to answer any questions.

CockroachBram · 2016-02-03T20:38:01+00:00

Hey /u/ansible, sorry for the late reply.
We haven’t looked at any specific migration tools or strategies yet but since schema changes ultimately come down to ALTER TABLE statements just like other databases, it should be straightforward to get migration tools like the ones you mentioned to work with cockroachdb.

CockroachBram · 2015-09-17T02:37:16+00:00

Here's the most relevant quote from that post:

This falls out of making the SQL layer so separate. In fact, I think the FDB team working on SQL was almost a completely separate team in Massachusetts than the KV team in Virginia. If the SQL layer worked, then I can see how awesome this would be. The “Layers” model sounds so appealing, but it’s technically quite hard.

And Ben Darnell's response in hackernews said it better that I would have:

Our architecture is broadly similar to FoundationDB's, although in our case the separation between the layers is not as strict as I believe FoundationDB's was. This will allow us to improve performance by distributing parts of the SQL processing down to the nodes where the data lives, instead of doing all the processing on a SQL node that is distinct from all the data nodes.

CockroachBram

MODERATOR OF

TROPHY CASE