Aurora, AWS’s managed MySQL and PostgreSQL database service, is removing an remove feature. As a association announced today, a new Aurora Backtrack underline will concede developers to “turn behind time.” For now, this usually works for MySQL databases, though. Developers have to opt in to this underline and it usually works for newly combined database clusters or clusters that have been easy from backup.
The use does this by gripping a record of all exchange for a set volume of time (up to 72 hours). When things go bad after we forsaken a wrong list in your prolongation database, we simply postponement your focus and name a indicate in time that we wish to go behind to. Aurora will afterwards postponement a database, too, tighten all open connectors and dump anything that hasn’t been committed yet, before rolling behind to a state before a blunder occurred.
Being means to retreat exchange isn’t totally new, of course. Many a database complement has implemented some chronicle of this already, including MySQL, nonetheless they are mostly distant some-more singular in range compared to what AWS announced today.
As AWS Chief Evangelist Jeff Barr annals in today’s announcement, disaster liberation isn’t a usually use box here. “I’m certain we can consider of some artistic and non-obvious use cases for this cold new feature,” he writes. “For example, we could use it to revive a exam database after using a exam that creates changes to a database. You can trigger a replacement from a API or a CLI, creation it easy to confederate into your existent exam framework.”
Aurora Backtrack is now accessible to all developers. It will cost about $0.012 per one million change annals for databases hosted in a company’s U.S. regions, with somewhat aloft prices in Europe and Asia.