> This is the story of how we seamlessly upgraded our production fleet to MySQL 8.0. Was it seamless? I recall GitHub being down a bunch lately, and even though the downtime is unrelated to the db upgrade, from the outside looking in, I don't know that I'd lean that hard on having done that seamlessly.
There are two possibilities: 1. The entire premise of the blogpost is completely fabricated and they are lying through their teeth. 2. The downtime was unrelated, from a product that doesn't actually have the best track record here in general. So ... what do you think?
Upgrading GitHub.com to MySQL 8.0
11–14 of 14 posts
Re: Upgrading GitHub.com to MySQL 8.0
#12Re: Upgrading GitHub.com to MySQL 8.0
#13Earlier quoted context omitted.
There are two possibilities: 1. The entire premise of the blogpost is completely fabricated and they are lying through their teeth. 2. The downtime was unrelated, from a product that doesn't actually have the best track record here in general. So ... what do you think?
or 3) Microsoft and GitHub are huge corporations where the left hand doesn't know what the right hand is doing. Writing corporate communications is hard, but it doesn't mean we shouldn't call out mistakes when they happen.
Re: Upgrading GitHub.com to MySQL 8.0
#14Earlier quoted context omitted.
or 3) Microsoft and GitHub are huge corporations where the left hand doesn't know what the right hand is doing. Writing corporate communications is hard, but it doesn't mean we shouldn't call out mistakes when they happen.
Are you genuinely trying to suggest that the people who did the migration don't know if it caused an outage or not?