Gitlab 500 error
I have growing concerns over GitLab.  I appreciate the openness and forthrightness of their handling of these sorts of incidents and in regard to other issues, but there comes a point where none of that matters if the product itself is inherently unreliable.  This post isn&#x27;t about any one incident, including this one, but an ongoing trend that I don&#x27;t get the sense is improving.<p>To be completely fair, I&#x27;m on the free plans and have no rightful expectation of any sort of performance level.  Having said that, I have considered moving to paid tiers, and I do advise others in regard to these sorts of services (whether cloud based or on-premise).  Every time I see a planned maintenance, of &quot;under 1m&quot;, I simply realize that I shouldn&#x27;t plan anything important for GitLab that day.  I can&#x27;t see that this would be any different with GitLab.com paid plans and I have to imagine there is something inherently difficult in managing the software if the developer of that software has issues with common maintenance; this colors my impressions of what this might be like in-house.  It seems a beast, I get that there are scaling issues that are different between something like gitlab.com and GitLab on-premise, but history of these things is coloring my impression.<p>At some point moving fast and breaking things needs to give way to the pursuit of enough stability that users aren&#x27;t overly concerned about whether or not the tools they depend on, or more importantly the data they&#x27;re storing, are regularly at risk.<p>I don&#x27;t want to buy services&#x2F;products from a company that is just trustworthy and open when things go wrong.  I want to buy services&#x2F;products from companies that only need to prove those qualities with some rarity.