5 ms·
I dont remember Google's Search Engine had outages. ( May be once in the past 10 years ) Why is it all the other products, from GCP to Google Sheet had more out
by ksec 7y ago
I dont remember Google's Search Engine had outages. ( May be once in the past 10 years ) Why is it all the other products, from GCP to Google Sheet had more outages?
And Google was suppose to compete with Microsoft Azure or Office 365?
- draugadrotten 7y agoOffice 365 has multiple outages daily, so are you sure that was a good example?
- lxgr 7y agoWithout knowing anything about the internals, I would assume that Sheets is significantly more stateful than search. I wouldn't notice Google rerouting my search queries to a slightly stale cluster in a different data center, but they can hardly serve me someone else's spreadsheets until consistency has been restored.
- chx 7y agoThere was a Google Search outage last September. Eg.: https://twitter.com/iittmee/status/1173772524573908997 https://twitter.com/iittmee/status/1173772524573908997 https://twitter.com/cryptoITGuy/status/1173773323970523136 https://twitter.com/cryptoITGuy/status/1173773323970523136 Not even specific to Google, but a product like Search has less outages because it doesn't require authentication / authorization checks, one search requires very little network bandwidth (unlike say YouTube) and can even work if some / most / all systems needs to go into a read only mode.
- liamdiprose 7y agoFrom Google's Site Reliability Engineering book[1]: > SRE’s goal is no longer "zero outages"; rather, SREs and product developers aim to spend the error budget getting maximum feature velocity. This change makes all the difference. An outage is no longer a "bad" thing—it is an expected part of the process of innovation, and an occurrence that both development and SRE teams manage rather than fear. I suspect Search has a lower error budget than Sheets. [1] https://landing.google.com/sre/sre-book/chapters/introduction/ https://landing.google.com/sre/sre-book/chapters/introductio...
- JohnFen 7y ago> An outage is no longer a "bad" thing—it is an expected part of the process of innovation, and an occurrence that both development and SRE teams manage rather than fear. As a user, outages are always bad things. That Google's SRE team thinks otherwise is chilling.
- skybrian 7y agoYou could set the failure budget really low if you never want any new features, but many users do want new releases now and then.
- joshuamorton 7y agoOf course outages are bad. But if the choice is "our service occasionally goes down" and "we never release new features", you may accept the risk of occasionally going down. So yeah, outages are always bad, but the alternatives can be worse.
- JohnFen 7y ago> if the choice is "our service occasionally goes down" and "we never release new features", you may accept the risk of occasionally going down. I don't think that I would, because I don't accept the premise of that being the necessary choice. It's just the choice that the providers deign to offer for economic reasons. But my objection isn't that there should be zero downtime. My objection is the idea that a service provider considers any downtime to be acceptable.
- joshuamorton 7y ago> My objection is the idea that a service provider considers any downtime to be acceptable. If you don't view any downtime to be acceptable, the logical thing to do is invest all of your resources into reducing downtime. This means solely investing in reliability infrastructure, redundancy, and making few or no changes to the system, since change introduces failure. Since no service does that, the logical conclusion is that very few people actually consider any downtime unacceptable. Broadly speaking, I can think of literally no service that advertises "zero downtime". Cold storage gets close, but even they offer a measly 12 or 16 9s of reliability. In other words, reliability is a business goal, much like any other business goal. Trying to achieve "perfect" reliability with limited resources isn't a good time. So looking at error budgets empowers SREs. You can go to leaders and say "hey we're exceeding our error budget, so we not making any more changes and only working on reliability until we're back within our agreed reliability."
- azurezyq 7y agoWell, actually Google search engine "outages" are fairly common, they are just less visible. Examples: Single data center outage: Search -> load balancers handle that just fine Cloud -> zone or sub-zone outage Backend failure: Search -> cache should handle that Cloud -> outage Data update failure: Search -> stale search results Cloud -> outage Office 365 also has issues, they can be minimized but cannot be eliminated: https://twitter.com/msft365status?lang=en https://twitter.com/msft365status?lang=en