LevelDB VS cockroach

I'm partial to how cleanly written https://github.com/google/leveldb is. It is a reasonable size to fully read & grok in not too long.

[4] leveldb/doc/impl.md at main · google/leveldb. GitHub. Retrieved October 21, 2023 from https://github.com/google/leveldb/blob/main/doc/impl.md

git clone https://github.com/google/leveldb.git

leveldb?

goleveldb - Implementation of the LevelDB key/value database in Go.

CockroachDB is an open source distributed SQL database designed for scalability and resilience. While it offers SQL databases, CockroachDB is also compatible with PostgreSQL.

cockroachdb might be close: https://github.com/cockroachdb/cockroach

CockroachDB - SQL

For example, when you create a serverless postgres database with a platform like CockroachDB or Neon, you effectively get a connection string with a strong password. Anyone can connect to your database from anywhere so long as they have the right connection string. There are no security settings in these services to change this behavior.

> Yes you can on the android emulator. The biggest issue is compu arch in that case.

I can also download VirtualBox and run all Windows programs, that would mean that all Windows apps are Linux apps?

> Yes you can for the most part

You can't statically link glibc: https://github.com/cockroachdb/cockroach/issues/3392

glibc can break stuff: https://www.gamingonlinux.com/2022/08/valve-dev-understandab...

I had binaries break because the newer version if openssl was put under a slightly different name.

Also, worth noting, if you're already using PostgreSQL (or plan to) you might want to take a look at https://www.cockroachlabs.com/ they have a free tier too and CockroachDB has a PostgreSQL interface.

I know that some projects like cockroach use custom build tools like bazel. But we actually really like to use to be able to build our projects simply with the great go toolchain and don't really aim to dive deep into custom build solutions.

CockroachDB is designed to be globally distributed. It has to handle causality when resolving collisions. It has to account for having a write operation to arrive after another and still have time priority because it was sent out a few milliseconds earlier.

Cockroachdb created a go runtime patch which measures the Grunning time of a goroutine: https://github.com/cockroachdb/cockroach/pull/82356. It doesn't entirely solve the problem though.

Our entire backend is written in Go. We've built a platform that allows other companies to offer automatic data syncing to their customers' data warehouses. Go works great for building distributed systems like this (see K8s). We're not the only ones in the space building data intensive applications with Go. Pachyderm, Pinecone, Cockroach Labs and are all also doing it. We've been quite happy with how Go has worked for us.