I would add https://github.com/gaul/s3proxy to your list. - Source: Hacker News / 2 months ago
* data state - this is contents of both your data and metadata at a given point in time. if your data doesn't fit into a single database, this can be difficult to manage. We use this technology to help us: https://lakefs.io/. - Source: Hacker News / 10 months ago
Saltcured, find these comments super insightful! > Yeah, there's a lot of hidden magic/assumptions in having a "writable snapshot of a specific version" of production data. That's absolutely a huge assumption. This technology has been a game changer for us: https://lakefs.io/ > It becomes a headache when there is too much contention to use these sandboxes, or too much manual effort to reset them to a desired... - Source: Hacker News / 10 months ago
You should not store your data in git itself, but rather use git to version your data sets. The currently best option for that is (IMHO) https://lakefs.io though there are a few others in various states of usability/maturity. Source: about 1 year ago
I mean if you're ready to adopt a new framework into your ecosystem this is one of the major usecases for LakeFS. Source: over 1 year ago
Also in the same vein, check out https://lakefs.io/. - Source: Hacker News / almost 2 years ago
Do you know an article comparing LakeFS to other products?
Suggest a link to a post with product alternatives.
This is an informative page about LakeFS. You can review and discuss the product here. The primary details have not been verified within the last quarter, and they might be outdated. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.