
There's always batbucket! https://batbucket.org/
Atlassian's code version control system Bitbucket has been suffering an ongoing failure in its storage layer, affecting developers across the globe. Problems arose yesterday (January 9) at 13:47 UTC, when the service website performance and SSH/HTTPS transactions slowed. After four hours of degraded performance, Bitbucket said …
"@bitbucket is really making our lives hell today. And before you bitch, yes, we pay for it."
That's your own fault for giving a 3rd party the responsibility for handling something you really should keep in house, and it's your own fault for not having a back up plan in place for such an event.
Maybe the plan is to let the devs twiddle their fingers: the cost of them playing doom for a few hours being cheaper than the cost of employing people to manage an in-house system 24/7 (with the attendant risk that an outage might still leave devs playing doom).
I'd want it all in house myself. But I know a old-time controlfreakosaurus.
In-house systems tend usually to be simpler because they don't have to support millions of devs, which makes them more stable and easier to fix. Also, if your system fails, mine usually keeps on working, being separated.
Decentralization had its benefits, it looks now they are forgotten, and to save a few dimes everybody is willingly to puts all of his eggs in someone else's basket.
It's good that for security reason we are forbidden to store company IP outside the company systems... so our manglement can't awake with bright ideas...
Have they applied patches and seeing the effects of performance hit on systems that were previously running a bit to close to the limit for comfort?
Quite a few systems I am aware of that were ticking over, just about getting by on only had about 20-30% "headroom" are suffering squeaky bum time after patching and seeing performance nose dive on I/O intensive stuff (hence AC!)
Or is it unrelated coincidence?
If its unrelated, they should have just seized the opportunity and cynically blamed the patches anyway, isn't that sleaziness what PR people get paid for?
All development stops for Millennials when bitbucket goes down. Older developers just don't notice - carry on being productive as usual! You know - getting stuff done. Millennial developers oil their beards and tend to their man buns whilst moaning on twitter.