They are still pretty limited compared to what's in the enterprise version, but it's not right to say basic backups are closed source and have never been there.
> 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.
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.
It means that you'd use a different ID to access each document. Each document's Durable Object would run the same code as part of the same namespace of Durable Objects, but have their own in-memory and durable state. Check out the docs for a bit more context: https://developers.cloudflare.com/workers/learning/using-dur...
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.
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.
WAN-optimized consensus protocols like Mencius and Egalitarian Paxos indeed are better for writes because any node can commit a write in one round trip, but they don't allow for reads with zero round trips. Every read must go through the consensus machinery in order to ensure consistency, whereas in CockroachDB the leaseholder can serve reads without needing to consult other nodes.
It helps with both, but is more dramatic for reads.
Reads go from 1 RTT to 0 RTTs, while writes go from 2 RTTs to 1 RTT. For example, consider a cluster in which the nodes are 200ms RTT away from each other.
* A read will take 200ms if the leaseholder isn't in the local datacenter vs single-digit milliseconds if it is local.
* A write will take 400ms if the leaseholder isn't in the local datacenter vs 200 milliseconds if it is local.
The write takes 400ms because it takes 100ms to get from the local datacenter to leaseholder, 200ms to reach consensus (the leaseholder needs to send a request to and get a response from one of the followers), and another 100ms for the response from the leaseholder to get back to the local datacenter where the request originated.
They are still pretty limited compared to what's in the enterprise version, but it's not right to say basic backups are closed source and have never been there.