Ultimately, they selected CockroachDB, as described in "RFD 110: CockroachDB for the control plane database" [1]. Now, published just yesterday, "RDD 508: Whither CockroachDB?" [2] discusses what to do in light of Cockroach going proprietary.
I'm getting increasingly nervous about baking in assumptions on software that doesn't have a strong guarantee of staying open source. Foundations like the CNCF help here, where projects are assigned ownership to the foundation.
There is a middle ground though. It's not practical to only build on top of foundation-owned software. So a metric I use these days is to consider the cost of replacement or fork maintenance, combined with how likely I think a license change would be, as part of evaluation.
Even with the Apache foundation therenis no guarantee they’ll be maintainers for support and active development. Only guarantee is a company that is profitable but doesn’t want more money…
Maybe people should be getting nervous that the whole flower power mentality of FOSS doesn't really scale when there are bills to pay, and families to nurture.
> Based on past experience, the reputation of a system or stories about it being used by other organizations are weak data points. We will want to independently verify any properties we care about.
I was curious to know what type of tool this is built on. Sounds like it's a static site generator that can process AsciiDoc, but I don't have any more detail than that. The links to GitHub repos in section 5 were all broken - maybe it's private?
It's unfortunate that page briefly flashes some text and goes blank
leaving an error in the browser console
Uncaught ReferenceError: TextEncoderStream is not defined
<anonymous> https://docs.oxide.computer/guides/introduction:18
Error: Minified React error #423; visit https://reactjs.org/docs/error-decoder.html?invariant=423
for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
zh https://docs.oxide.computer/assets/components-BfA3Cgf2.js:40
Thanks for the bug report. We could stand to have a better catch-all error page for this case.
Looks like this browser API is used by Remix’s new Single Fetch feature, which coincidentally we just started using last week. Sorry we broke the site for you. We don’t have as clear of a browser support policy as we probably should, but if we did, I doubt we would be guaranteeing support for two year old browsers unless we had a customer request for it.
[1]: https://rfd.shared.oxide.computer/rfd/0110 [2]: https://rfd.shared.oxide.computer/rfd/0508