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

Said another way:

  - You have a system whereby every instance has a 75%-79% uptime.

  - Each instance's 21%-25% daily scheduled maintenance window can (generally) be arbitrarily-scheduled by the ops team.
How do you near guarantee that there's always one instance available?

If you said:

  "manage a redundant cluster of at least 2 instances with non-overlapping maintenance windows" 
Then you were correct!

BONUS QUESTIONS:

Q: What's the max number of ice cream machines found in a McDonald's location?

Q: What's the cluster size of the McDonald's ice cream monitoring system?

Q: How much money does McDonald's have?

Q: Why the fuck?

If you said: "1", "at least 3", "metric fuck-tons", and "I don't know", respectively, then you were correct!



The answer to #4 is probably that the goal isn't to always have ice cream. The goal is to run a profitable business.

Doubling the cost of the ice cream infrastructure to avoid a 25% downtime may not be a profitable venture -- especially if the downtime is scheduled to occur while the store is closed.


Shelf-space is in high-demand and those machines aren't cheap.


McDonalds is in the real estate business (letting buildings), fast food is just a side order.


Aren't the stores franchise's, with the individual stores owned by the relevant franchisee?


The operations are mostly franchised, but the corp owns many of the buildings and plots of lands that they are located on.

https://www.mcdonalds.com/us/en-us/about-us/franchising/real...


Also, you can use data to schedule the maintenance when the probability of someone ordering ice cream is low. That 21-25% downtime results in significantly fewer people wanting ice cream not being able to get it.




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

Search: