News for hackers. Stuff that matters.

A comment on Hold off on AWS Aurora and Postgres until further notice. Parent comment

Re:Hold off on AWS Aurora and Postgres until further notice by mrep on Monday January 01, 2018 @10:06PM (#16049548)
That's lucky. Was your service down for the entire time until the data was recovered?
[ Parent | on HN ]
Re:Hold off on AWS Aurora and Postgres until further notice by sudhirj on Tuesday January 02, 2018 @12:06AM (#16049997)
We moved to a new DB as a clean slate, took fresh orders, and then merged the old ones in as they became available. Was able to do that because all primary keys were uuids and the order history API was being served somewhere else.
[ Parent | on HN ]
Re:Hold off on AWS Aurora and Postgres until further notice by mrep on Tuesday January 02, 2018 @12:37AM (#16050101)
How did you handle other tables like users and sessions?
[ Parent | on HN ]
Re:Hold off on AWS Aurora and Postgres until further notice by sudhirj on Tuesday January 02, 2018 @04:29AM (#16050877)
This microservice didn't have them, but even they're all keyed by UUID, so it's possible to start a clean slate pretty fast. Filling in existing users later should also be easy, the problems will occur if and when users try to sign up again with the same key (email / FBid etc).
[ Parent | on HN ]