3 ms·
Doesn't 1 second of database downtime just mean that a ticket that is scanned during that 1 second window will take 1.5-2 seconds to scan instead of, say, 500ms
by subarctic 3y ago
Doesn't 1 second of database downtime just mean that a ticket that is scanned during that 1 second window will take 1.5-2 seconds to scan instead of, say, 500ms? Why would that result in 10 minutes of troubleshooting?
- abhibeckert 3y agoBecause when it doesn't work, they'll get an error message, and then they will try to figure out how to fix the error message. These aren't tech savvy people. You don't hire an IT person to stand at a door scanning a thousand QR codes for 20 minutes three nights a week.
- ses1984 3y agoWhy would you immediately show an error message instead of some kind of background retry? Or at the very least the message should tell the operator to retry.
- emeril 3y agoit isn't downtime he's as concerned about as it's about speed he could build in behavior to retry/wait for several seconds before erroring out but his selling point is speed seemingly (with little risk of sale negatives/positives/theft)
- jtc331 3y agoThat doesn’t have to incur actual downtime if you use pgbouncer in front of Postgres and pause the pool.