|
|
|
|
|
|
by LukeEF
2201 days ago
|
|
|
Very interesting. I work with TerminusDB and we've been thinking a lot about how to apply a revision control semantic graph db to ML tasks. The whole MLOps process is fragmented and we think a collaborative revision control (like git but for data) that allows all of the parts to work together (data engineer, data scientist, ML engineer) could be very useful. |
|
|
A git for data like you describe seems intuitively (but should be well defined) to be a technology very useful for many things. From safely versioning knowledge a la mediawiki to versioning business data in DBs and making it seamlesss for all the human pipeline (data engineer, data scientist, ML engineer).
Actually I have a startup Idea that would require somthing similar yet different: I would need both version control for user data AND guaranteed immutability of what users have wrote. It would allow users to trust that the server cannot modify their data. For such a use case, the first things that comes to mind are blokchains but the technology feels too limiting. The only offer that I'm aware of as a general SQL DB is https://aws.amazon.com/qldb/
BTW git but for data is an idea that has a lot of competing implementations, it would be nice for your landing page to explain what differentiates you from e.g -> https://news.ycombinator.com/item?id=22731928
Anyway I wish you a good luck in this fun and probably useful project !