Git repositories seem like an elegant solution for package registry data. Pull requests for governance, version history for free, distributed by design. But as registries grow, the cracks appear.
They aren’t using git as a database, they’re using it as revision history. The database is whatever they decide to store in git. For crates.io, for example, they use JSON files in directories.
If you put an sqlite database in git, you are wouldn’t say “git is the database”, and that’s true here too.
That said, yeah, you shouldn’t roll your own database. Take your source code (JSON from crates.io) from git, and compile it into an sqlite file (for example) for download.
They aren’t using git as a database, they’re using it as revision history. The database is whatever they decide to store in git. For crates.io, for example, they use JSON files in directories.
If you put an sqlite database in git, you are wouldn’t say “git is the database”, and that’s true here too.
That said, yeah, you shouldn’t roll your own database. Take your source code (JSON from crates.io) from git, and compile it into an sqlite file (for example) for download.