4 ms·
I didn't see a specific answer for the current setup referenced in the article that would have netted zero downtime. It's true the table wasn't available for 1
by buckbova 11y ago
I didn't see a specific answer for the current setup referenced in the article that would have netted zero downtime.
It's true the table wasn't available for 15 seconds, but current connections weren't dropped/lost, so a robust interface with the API should survive a 15 second delay.
Shouldn't a system like this be built to handle long delays?
- Sinjo 11y agoWe can't count on a user (either in the browser or using the API) waiting around that long. Even some of our own services time out more aggressively than that. Those situations can be smoothed over with retries, but we try pretty hard to avoid delays like this in the first place.