Personally I think I'm more drawn to the dotmesh approach (https://docs.dotmesh.com/concepts/architecture/ https://docs.dotmesh.com/concepts/architecture/), but

Personally I think I'm more drawn to the dotmesh approach (https://docs.dotmesh.com/concepts/architecture/ https://docs.dotmesh.com/concepts/architecture/), but the one problem data has is as it gets massive it becomes really hard to move it around and I guess that's where trying to layer git like workflows on top of it become intractable. It's like data has it's own gravity and often times it is just easier to bring other things to the data, rather than the other way around. IIRC Bryan Cantrill said something similar about data when Joyent was developing their object storage system Manta (https://www.youtube.com/watch?v=79fvDDPaIoY); https://www.youtube.com/watch?v=79fvDDPaIoY); ergo, perhaps the Splitgraph approach will meet with better success.