3 ms·
I have pressureNET running on EC2 in US-East. It's collecting data about Sandy from a bunch of Android users in the region, and I only realized a few hours ago
by cryptoz 14y ago
I have pressureNET running on EC2 in US-East. It's collecting data about Sandy from a bunch of Android users in the region, and I only realized a few hours ago that...it's gonna get hit by Sandy. I'm not sure what to do.
The Android app has a hardcoded server URL to the DNS of my instance. If the server goes down, and I prepare a backup, all my users will still be sending to the old, dead server (assuming Sandy takes out AWS in that region). So I can also update the app and give it a new server url. But I'm going to lose many hours of valuable hurricane data as users take time to get the update, etc.
Does anyone have any thoughts on how I can handle this?
I realize my mistakes and know how to fix them for next time, and my current data is obviously backed up. But for incoming data...am I screwed?
Edit: I have an idea. I'll update the app and give it a backup URL to use only if the main one is non-responsive. Then I'll publish the update and cross my fingers.
- timdorr 14y agoEdit: Rewrote my entire comment... The delay on the app side should only be 15-30 minutes. Use a replication database (much like the Postgres follower system on Heroku) to ensure no loss of data and you should be fine.
- deleted 14y ago[deleted]
- ejdyksen 14y agoBefore you need to, set your DNS TTL as low as you can.