Recently (november 2016), ClusterHQ released a new tool called
fli that seem to be promising. I have not tried it yet, but it seems it plays well with many database system (mysql, mongodb, elastic, etc).
Moreover, I do not know if it plays well with GIT and it will certainly be anoying to work with 2 cli toolset, 2 revision system, 2 repository ... for each project. It would be important to manage both data and text with the same system if one wants to keep the essential improvement provided by GIT to projet management and decentralized/collaborative work.
GIT design is fine for data management. Branches, merges, pull requests, etc. and more recent submodules and subworktree are powerful features that radically transformed our day-to-day workflow. The only problem with GIT fot data is that its actual implementation is focused on text files. It track changes with an extensive use
diff. That is fine for code or writing projects, but it is clearly not an optimal way to manage big datasets.
A possible improvement within GIT itself that could enable its use for data would be to simply replace everything diff operation applied to a database with something more appropriate for this type of dataformat.