Hacker News new | past | comments | ask | show | jobs | submit login

This is exactly my concern. There is no production system I have ever worked on which this feature would ever be used.

What if you had an e-commerce site? Other customers were placing orders, right? Credit cards being charged? You didn't catch your mistake instantly. So you have a window of maybe, 5 minutes or a hour in which other things happened. You can't simply forget those other transactions and throw away the data.




There have been many well publicized events where a production database was lost, or in some way corrupted. I’ve lived through one such event myself. When that happens, you usually go to a backup, and typically run into two problems:

1) Point in time back ups can be hours old.

2) More importantly, “backups” are useless, it’s the “restores” that are valuable. And very few organizations have a well practiced muscle memory for restoring from a backup.

A turn key restore solution, with a per second granularity can both significantly decrease the loss window, and recovery time. Hope nobody gets to use it, but when you have, it can be a difference between a big and a small outage.


Consider non-production use cases... run a test suite and then reset the data back to a pristine state after each run.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: