SQLite is fine right up until you want concurrent writers. Once you need multiple users, cross-host access, or anything that looks like shared infra instead of a local cache, the file-locking model stops being cute and starts setting the rules for the whole design. For collaborative versioning, Postgres makes more sense.

▲

brigandish an hour ago | parent [-]

For a distributed VCS, what would be the need for such things? Even if it were a really big project, how many writes could be going on that this becomes a bottleneck? I don't see it but maybe you have a situation in mind.

	▲	lelanthran 8 minutes ago \| parent \| next [-]
		In the current environment, even a distributed VCS may have concurrent agents modifying it on different branches.
	▲	ImGajeed76 an hour ago \| parent \| prev [-]
		The problem i faced is mostly importing large repos. But normal use should be fine.