5 hours downtime just to add a new product
Little bit of industry insight here:
It might seem a bit "odd" that one or two minor items added to a store would require such massive downtime. This is the not the way that these products are deployed however.
The reason why you have a 5 hour downtime is because that's how much time it takes for the deployment of the new DB (containing the new items) and new bits to be delivered into the Production environment.
There is lots of steps to ensure that:
1. Dont get fired.
2. Things like stop services, start services are done manually. Most of the steps are basically executed manually even if it is scripted or automated. They just dont fly with that kind of risk in production.
3. Able to stop and rollback incase issue found.
So realistically this wasn't an Apple store update - this was a release to the Apple store that required deving, testing, and then manual and very cautious push to production. In short, they are not using a eCommerce front end to make the change in production (even if they do that during dev).
Because I hate to say it but NOBODY wants to be in the hot seat losing their job because they accidentally published the new item incorrectly, costing the company face and probably money honoring some orders.
-v
PS> To that effect, the price of the product was in the testing environments before it went live - meaning people internally are NOT leaking this even though they see it.