A programmable data cloud
It will ship something wrong. You get a button.
Regions
If you build on their backend, their outage is yours. So it isn’t anywhere in particular. Five regions hold the data and run the functions, and none of them matters. Take one away.
Every region writes its own. Flip a switch.
The latencies are real: your browser asks each of the five regions every few seconds, and the number is how long the answer took. The switches are a picture: nothing goes dark in that fleet. In it, a region’s writes move to another when its lease runs out, in under a minute, and a majority of the regions has to be standing to decide who takes them.
Waiting for three regions
A latency is a distance with a little added. Where your traffic reaches each region by a way of its own, each gets a ring as far out as its latency allows, and you are about where the rings agree. Where it all comes in by the nearest region, that one number is all there is. The clock this device is set to says which part of that you are in. It is all worked out in this browser: nothing about where you are is sent to us. Drag the globe to turn it.
Real-time
A channel makes you say everything twice: once to write it, and once to tell everyone it was written. Here you only write. Whoever is holding an answer that just went wrong gets the right one.
That is the whole vocabulary. One flag, on a call you were already making.