# Why did you choose to use a sqlite db?

**URL:** <https://forum.storj.io/t/why-did-you-choose-to-use-a-sqlite-db/278>\
**Category:** design draft\
**Tags:** v3-alpha, storagenode\
**Created:** [July 1, 2019, 9:16pm UTC](https://forum.storj.io/t/why-did-you-choose-to-use-a-sqlite-db/278 "2019-07-01T21:16:12Z")\
**Posts on this page:** 1\
**Page:** 2

<div class="post-metadata">

**Author:** ![hashbackup](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/hashbackup/32/9034_2.png) [@hashbackup](https://forum.storj.io/u/hashbackup)\
**Post date:** [September 19, 2021, 3:26pm UTC](https://forum.storj.io/t/why-did-you-choose-to-use-a-sqlite-db/278/21 "2021-09-19T15:26:19Z")

</div>

HashBackup uses SQLite to store file metadata: timestamps, permissions, block reference counts, pathnames, etc. The largest backup I’ve had reported to me is a 121TB backup that created a 17GB SQLite database. Performance remained excellent.

I’m not familiar with the typical size of databases Storj uses, so maybe 17GB is not that big. Just adding it here as a performance datapoint.

[Previous page](https://forum.storj.io/t/why-did-you-choose-to-use-a-sqlite-db/278.md?page=1)