This won't work for usual database usecases. This is meant for interactive work with data same way you work with code. Who needs that? Data scientists working

This won't work for usual database usecases. This is meant for interactive work with data same way you work with code. Who needs that? Data scientists working with large datasets. You want to be able to update data without redownloading everything. Also make your local changes (some data cleaning) and propose your updates upstream same way you would with git. Having many people working interactively with data is common here. One of the companies I work with provided set of data distributed to their partners on a daily basis. Once it grew larger, downloading everything daily became an issue. So that would be desirable, I have large data model that I need to deploy to production and update once in a while. For code, network usage is kept to minimum because we have git. For data, options are limited. As with git, it is something that once you have, you will find a lot of usecases that make life easier and open many new doors.