Re:January 28th Incident Report
by dsmithatx on Wednesday February 03, 2016 @04:50PM
(#11030060)
If only Bitbucket could give such comprehensive reports. A few months back outages seemed almost daily. Things are more stable now. I hope for the long term.
[ Parent
| on HN ]
Isn't BB's problem basically that there are too many users? GH's outage writeup is cool, because it's a one off and it can be analysed. When BB is just overloaded for a long time and needs more power, it's not going to be very interesting.
(unless I missed some specific non capacity related outages?)
Maybe. BitBucket was also an acquisition so for some time I believe there was a lack of resource provided to them and there was a huge technical debt/integration effort required. At this very time, I don't know if Atlassian actually care much about BitBucket. They are probably more concerned about delivering Stash than BitBucket, my wild guess.
I was an active BB user a couple years ago, and the project I worked on would hg clone from BB many times a day so I would be the first one to notice a 503 or whatever error coming from their service. Typically I would see one or two outage per month, some last a few minutes, some last several hours. Most of the time the outage impacted git/hg checkout, so I think that was their technical bottleneck.
Re:January 28th Incident Report
by rajksarkar on Wednesday February 03, 2016 @06:17PM
(#11030712)
We are actually investing a lot in Bitbucket: http://blog.bitbucket.org/2015/09/22/1-in-3-fortune-500-comp...
FYI, Stash is now Bitbucket Server, and the plan as I've heard it is to work towards feature parity between the two.
Re:January 28th Incident Report
by mattdeboard on Wednesday February 03, 2016 @05:39PM
(#11030441)
We use Stash and it is surprisingly not bad at all. Github is much more polished but for code browsing and review, it does that which it is supposed to do.