Skip to content
spredrstatus
sign inget started
Documentation index
How it works

If a machine falls

You don't have to do anything. spredr notices, puts your service on another machine in the same region and it answers again in about 4 minutes.

spredr asks three ways before it moves anythingthe machinea request like your customers'the provider1a machinestops answering2it is confirmedtwo ways, oneis not enough3another machinetakes over,in your region4your servicestarts there,on its release5answers againabout 4 minutesafter the fall6all goes backto its machine onceit recoversabout 4 minutes from the fall to answering again
spredr asks three ways firstthe machinethe providera request like your customers'1a machinestops answering 2it is confirmedtwo ways, one is not enough3another machinetakes over, in your region4your servicestarts there, on its release5answers againabout 4 minutes after the fall6all goes backto its machine once it recoversabout 4 minutes

Measured on real machines: about 4 minutes from the fall until your service answers again.

what you doNothing. spredr does it on its own.
how longAbout 4 minutes, measured on real machines.
whereIn the same region whenever there is room: your service stays close to your database.
no false alarmsA minute of bad network isn't enough: spredr confirms the fall in more than one way before moving anything.
what is lostWhat your service held only in memory. Keep in your database what you cannot lose.
nextA deployFrom your push to the new release.watchWatchingActivity, logs and risks.