a-robinson

> My current database is in a private subnet, it would be unfortunate to have to open it up to the world to take advantage of this.

Agreed, this is a big current limitation. As mentioned in the blog post, though, we'll be adding support for connecting into private networks via our other networking products (Cloudflare Tunnel and Magic WAN).

Misleading title -- it isn't claiming that there are any newsletters generating $22M a year individually. It's just saying that the top 27 (why 27?) newsletters in aggregate make at least that much.

Yes, exactly!

Storage is replicated across a handful of nearby sites. It does add some latency to writes, but that's preferable to Objects being offline or lost in the case of hardware or network failures.

There's no Jepsen testing in the works at the moment, but we'll see if it makes sense in the future.

With how often I've seen spaced repetition mentioned online recently, I'm starting to assume there's a grand conspiracy that's trying to use spaced repetition to trick me into remembering about spaced repetition.

In this case it actually makes sense because it's not easy to find a non-paywalled version of the paper.

To add on to that last point, you don't need to pick in advance which region or regions your code will run in. You push your code once, and it will run in whichever edge locations receive requests, potentially all 165+ locations if you have users sufficiently spread around the world.

Yeah, it appeared to just be general resource contention from having to share the machine -- CPU interrupts, less memory available, etc.

I'll note, though, that the 5% number is when using host networking for both Cockroach and the client load generator. Using GKE's default cluster networking through the Docker bridge is closer to 15% worse than running directly on equivalent non-Kubernetes VMs.