Provides a case study of the 'Corporate Shutdown' risk where a professional engineering team is suddenly removed from a project due to business failure.
After seven years of development, the commercial entity behind RethinkDB and the Horizon framework announced its shutdown in October 2016 due to an unsustainable business model. While a continuity plan was developed to transition the projects to an independent, community-driven open-source model, the core engineering team was hired by Stripe to work on different infrastructure problems. This case study illustrates the fragility of professionally-maintained open source when backed by a single venture-funded company, where corporate failure results in the immediate loss of a dedicated team for a critical data infrastructure project.
The company behind the project shut down, and while community continuity was planned, the core engineering team moved to a different company.
sudden loss of security maintenance and professional support for a core piece of data infrastructure
corporate failure is a high-impact, low-probability event that directly leads to the functional abandonment of professional-grade open source tools.
After more than seven years of development, the company behind RethinkDB is shutting down... ultimately unable to build a sustainable business.
Risk Guard evaluates technical health but doesn't track the 'Financial Health' or 'Runway' of the commercial entity behind a sponsored package.
Risk Guard would be better if it integrated signals regarding the corporate sponsor's financial stability (e.g., funding rounds, layoff news) as a leading indicator of project risk.