captheorem's profile picture. Wrong answers only

Tolerating partitions

@captheorem

Wrong answers only

Do you remember when you joined Twitter? I do! #MyTwitterAnniversary

captheorem's tweet image. Do you remember when you joined Twitter? I do! #MyTwitterAnniversary

I hope so.

eventual consistency means people will start getting all the great CAP theorem jokes



I say it's probably fine: - each object is single-threaded - each object exists in one place at a time Minimal coordination demands. But this sounds like it could potentially be a headache: - Durable Objects will combat this problem by auto-migrating

Cloudflare Workers Durable Objects opened a can of worms for me: blog.cloudflare.com/introducing-wo… It's a storage for the edge workers with: * low-latency * strong consistency * not zonal, but global replication. But CAP theorem says... 🤔 🤔 🤔



Tolerating partitions reposted

I have been asked this a great deal. I think the real issue is how *many* services you have, not their size. If you have a few, manage them how you like. When you have 100 or 1000 (or 1M like Google), you need infrastructure help, especially if you also want release velocity.

Cloudflare Workers Durable Objects opened a can of worms for me: blog.cloudflare.com/introducing-wo… It's a storage for the edge workers with: * low-latency * strong consistency * not zonal, but global replication. But CAP theorem says... 🤔 🤔 🤔



One does not simply abandon theorems.

Cloudflare Workers Durable Objects opened a can of worms for me: blog.cloudflare.com/introducing-wo… It's a storage for the edge workers with: * low-latency * strong consistency * not zonal, but global replication. But CAP theorem says... 🤔 🤔 🤔



United States Trends

Loading...

Something went wrong.


Something went wrong.