Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Now might be a good time to ponder a lasting solution. Clearly, we cannot trust AWS, or any other single provider, to stay up. What is the shortest, quickest to implement, path to actual high availability?

You would have to host your own software which can also fail, but then at least you could do something about it. For example, you could avoid changing things during critical times of your own business (e.g. a tradeshow), which is something no standard provider could do. You could also dial down consistency for the sake of availability, e.g. keep a lot of copies around even if some of them are often stale - more often than not this would work well enough for images.



High availability is improved by hosting in multiple AWS regions.

S3 offers alternative region replication functionality and you can use Cloudfront of another CDN to load balance between buckets


Yup, all of our fail overs worked flawlessly. You wouldn't even be able to tell if you didn't know.


But do you always serve files from S3? Wasn't the entire S3 down today? Or was it just some regions? I couldn't even connect to s3.amazonaws.com ...


Only one region, us-east.


How can you use Cloudfront to point to multiple buckets? I'm pretty sure each origin needs a path and Cloudfront serves the first path that matches.


I use a master and four mirror slaves. Then use round robin for reads. I used to have three slaves, but when two of them was down at the same time I got nervous and set up one more.


How does that work with S3? Your master and slaves are presumably just SQL databases, right? Or?


vps via different providers. think RAID but with VPS.


Quickest path? Use AWS (or similar). Outages happen. The more robust you want to be against outage, the more prep work you have to do. In order to have 'no outage', you have to do an incredible amount of work. There is no quick path.




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

Search: