 |
| Ask HN: How do big web sites roll out new versions? | ||
| recommended by 2 users | 2008 | 110 points by Bluem00 | distributed systems | original thread | | ||
The operations of big websites fascinate me. Sites such as http://highscalability.com/ give an glimpse into the architecture of Amazon, Twitter, and other large systems, but leave out the operations side. So, can anyone explain how they deploy new versions of their sites? For instance, I can't imagine Amazon choosing to go down for even a minute, so what do they do? Am I wrong? Thanks! | ||
| 2 users recommended this thread. What they said: |
| mpk Jan 3, 2009 | on: Ask HN: Best HN threads in '08? | context |
|
dkf May 3, 2010 | on: Deployment Infrastructure for Continuous Deployment at… | context
Yes, where we feel it's the best solution (our standard key-value store is voldemort). SQL changes are peer reviewed and applied with a set of scripts we have to make the process easier. This isn't integrated into the deployment service yet, but it's something we've talked about. http://news.ycombinator.com/item?id=411282 has a good description of something that's very similar to our SQL rollout policy: "only add columns to tables and new tables, never to remove anything, so the database can be upgraded hot, and the old code can continue to run on it, only the new code will see any new columns/tables." and "Once you are sure you are never going to roll back to the old code you can wipe out the old columns." This comment (and its author) http://news.ycombinator.com/item?id=411358 were formative in my views of service deployment. |
"Ask HN : How do big websites roll out new versions?" http://news.ycombinator.com/item?id=411282
Lots of interesting replies to that one.