Re:Tarsnap outage (July 2-3, 2023) postmortem
by zetalyrae on Thursday July 27, 2023 @08:39AM
(#36892544)
If you think creating a database schema is the software equivalent of the Long March, you should find another profession. Types are good, schemas are good, and nobody needs couldn't care less Unix cowboys who build everything out of bash and bailing wire.
Re:Tarsnap outage (July 2-3, 2023) postmortem
by HumanOstrich on Thursday July 27, 2023 @11:00AM
(#36894629)
This comment is unnecessarily antagonistic, and you are consistently and willfully missing all the points in your replies.
He could have set up a more complex architecture and paid much more in hosting costs over the years to overengineer the solution. What would the benefits be? It might have avoided this one outage or saved a few hours restoring the data. The drawbacks? Much more time developing and maintaining the solution and higher subscription costs for users.
The solutions you are familiar with and comfortable with are perfectly valid. But you are falling into the trap of thinking "what I'm familiar with and comfortable with is the only valid answer and everyone else is wrong and stupid".
Re:Tarsnap outage (July 2-3, 2023) postmortem
by dang on Thursday July 27, 2023 @02:15PM
(#36897907)
Please see https://news.ycombinator.com/item?id=36897868 and please stop posting in the flamewar style to HN. Regardless of how right you are / how much smarter you are or feel you are, it's exactly what the rules here ask you not to do. We're trying for a very different quality of conversation here.
Re:Tarsnap outage (July 2-3, 2023) postmortem
by zetalyrae on Thursday July 27, 2023 @06:11PM
(#36900831)
You're right, that was uncalled for. I apologize for lowering the quality of site.
Thanks for the kind reply.
Dumb is `aws s3 cp` and being done in 5 minutes.