CAP theorem

We can work with colleagues here at Amazon, retrofit systems that the world relies on with Hydro, show that it gives correctness guarantees that the previous code did not, and does not give up performance.

And we're talking about distributed systems here, and I think a lot of times when people get introduced to distributed systems, they get introduced to, like, the CAP theorem, and that becomes the overall thing of, like, how they think about the world, and there's always this discussion around whatever the investment is or whatever they're building.

What are the two things that they're guaranteeing out of the three? But I guess, like, you've been a proponent of the CALM theorem.

Like, how do those things relate? And I guess, like, how does CALM potentially change the conversation away from CAP?

Hmm.

So many questions are embedded in there.

So I'm gonna postpone the specific CAP versus CALM thing for a minute-

Mm-hmm

Do you know, this is probably getting too early into the weeds, but...

There is the CAP theorem, and I assume if you want to have a trustworthy central register of anything, then you need to prioritize the integrity of it.

I forgot which one of the letters it is.

What I'm getting at is that the compromise they chose to do is to have the single point of failure, that if that is down, then nothing else works.