I Deleted a Database in Production And I had no backup

I generally don’t mind these disaster stories as there’s usually useful information in there.<p>Not this one.<p>1. It isn’t a rite of passage to delete a production database, it’s an extreme accident &#x2F; fuck up. Stop normalising this. The guy literally deleted the machine without even thinking about the impact.<p>2. There was no backup. At all. Not even one. Not even one from a week ago. I can’t have any sympathy for someone hosting a production database without any backups running at all. A backup didn’t fail - they literally had purposefully not set up a backup.<p>3. Using a cloud provider and hosting your entire infrastructure on one virtual machine including your critical persistence layer with no replication. This is so stupid I can’t even begin to feel sympathy.<p>There’s nothing to be learned from this article other than the fact the author makes it a habit to implement bad practices.

I really dislike these &quot;I did dumb things, please give me likes&#x2F;up votes&#x2F;virtue points&quot; themed articles. We all know that you&#x27;re not supposed to get drunk and punch your wife or crash your boss&#x27;s fork lift doing donuts. When people do those sorts of things about it. Paying the stupid tax because you didn&#x27;t follow common sense practices and hosed a production database, caused downtime, cost your employer money, fell for a check fraud scheme, got your bike stolen, etc, etc, is not some badge of honor. Why do people tell stories about it as if it is?

The &quot;lesson&quot; of &quot;don&#x27;t put stateless and stateful on the same VM&quot; seems pretty off.