It's a well-known fact that Git is amazing for storing code. It is fast, reliable, flexible and keeps our project history nuzzled safely in its object database while we sleep soundly at night.
But what about storing more than code? Why not data? Much flexibility is gained by ditching traditional databases, but at what cost?
In this talk, we will explore the idea of harnessing Git as a data store.
We'll look at the benefits of using a schema-less data store, the incredible opportunity provided by having every change to every model versioned, plus all the crazy things that could be done with branching and merging changes to data.
We'll also learn about the challenges posed by using and scaling Git as a data store, such as concurrent access and distributing load.
Sign in to add slides, notes or videos to this session