News for hackers. Stuff that matters.
Re:Summary of the Amazon DynamoDB Service Disruption in US-E... by markus_zhang on Thursday October 23, 2025 @07:47PM (#45688968)
That’s pretty good. Our oncall is actually 24-hour for one week. On paper it looks very serious but even the best of us don’t really know everything so issues tend to lag to the morning. Neither do we get any compensation for it. Someone got a bad night and still need to logon next day. There is an informal understanding to relax a bit if the night is too bad, though.
Re:Summary of the Amazon DynamoDB Service Disruption in US-E... by dmoy on Thursday October 23, 2025 @09:42PM (#45689804)
I did 24hr-for-a-week oncall for 10+ years, do not recommend.

12-12 rotation in SRE is a lot more reasonable for humans

Re:Summary of the Amazon DynamoDB Service Disruption in US-E... by markus_zhang on Thursday October 23, 2025 @10:54PM (#45690253)
I agree. It sucks. And our schedule is actually 2 weeks in every five. One is secondary and the other is primary.
Re:Summary of the Amazon DynamoDB Service Disruption in US-E... by sandeepkd on Friday October 24, 2025 @12:38AM (#45690835)
Unfortunately 24hr-for-a-week seems to be default everywhere nowdays, its just not practical for serious type businesses. It just an indicator of how important is the UPTIME for a company.