News for hackers. Stuff that matters.
Re:Oxide: Control plane data storage requirements by willbicks on Saturday August 17, 2024 @01:16PM (#41276066)
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.

[1]: https://rfd.shared.oxide.computer/rfd/0110 [2]: https://rfd.shared.oxide.computer/rfd/0508

Re:Oxide: Control plane data storage requirements by cybrexalpha on Saturday August 17, 2024 @04:51PM (#41277852)
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.

Re:Oxide: Control plane data storage requirements by SOLAR_FIELDS on Saturday August 17, 2024 @05:11PM (#41277993)
Even with the CNCF badge there is no guarantee. See the sketchy ownership semi scandal over Linkerd
Re:Oxide: Control plane data storage requirements by Pet_Ant on Sunday August 18, 2024 @05:29AM (#41281220)
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…
Re:Oxide: Control plane data storage requirements by pjmlp on Wednesday August 21, 2024 @07:01AM (#41309000)
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.