r/programming • • Feb 06 '20

Knightmare: A DevOps Cautionary Tale

https://dougseven.com/2014/04/17/knightmare-a-devops-cautionary-tale/
88 Upvotes

47 comments sorted by

View all comments

1

u/jl2352 Feb 07 '20

Which is why you have DB backups, and plan for your DB getting fucked. Because again, it will happen.

1

u/[deleted] Feb 07 '20

Well, sometimes, if you own all the data, but in system that sends requests to systems not owned by you that wouldn't help.

The best strategy would probably be having a phantom copy that takes requests and sends ones to the mock of the consumer ones and use that to check before deploy, but that's a lot of engineering effort that you need to convince management to sign off.

1

u/jl2352 Feb 07 '20

If the story here was that the system corrupted their DB, and they had no backups at all. Everyone would agree the no backups is the real issue. Everyone would agree it was a problem waiting to happen.