What are /r/CockroachDB's favorite Products & Services?

From 3.5 billion Reddit comments

That's part of the appeal of the PostreSQL-compatible SQL API. https://www.cockroachlabs.com/docs/v21.1/postgresql-compatibility "CockroachDB is wire-compatible with PostgreSQL 13 and works with the majority of PostgreSQL database tools such as Dbeaver, Intellij, pgdump and so on. Consult this link https://www.cockroachlabs.com/docs/v21.1/third-party-database-tools for a full list of supported third-party database tools. CockroachDB also works with most PostgreSQL drivers and ORMs."

CockroachDB won't currently remove a node for being slow; it's up to the operator to monitor this and decommission the node if appropriate. Nodes are only removed automatically if they are completely down. See the FAQ for more on our failure recovery processes.

Related to this, I've been meaning to ask you guys about management of schema changes on the mailing list. Are there plans in this area yet? Will you support one of the existing tools like Squitch or Liquibase?

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.

Yes, using --advertise-port=26258 should make the third case work, although this is not widely used or well tested.

However, I don't think this is how bridge networks are supposed to be used. In a bridge network, each container gets its own IP. You should connect to those IPs instead of going through the docker daemon's port remapping on the host. You might remap one port to make it accessible to the host, but you don't need to map all of them.

Personally I feel like bridge networks add a lot of complexity for little value. I'd recommend either using host networking for simplicity or overlay networks when you need more complex routing (and use kubernetes or docker swarm to manage that overlay network). We have docs on kubernetes and docker swarm which I'd highly recommend instead of trying to set up a cluster with docker by hand (if you want to do it by hand, I'd stay away from docker).