<story><title>Database-less torrent website</title><url>https://boredcaveman.xyz/post/0x1_dbless-torrent-website.html</url></story><parent_chain></parent_chain><comment><author>ineedasername</author><text>The headline doesn&amp;#x27;t make much sense. There&amp;#x27;s still a database, what changes is simply where it&amp;#x27;s stored when in use. &amp;quot;Torrent Website w&amp;#x2F;o DB &lt;i&gt;Server&lt;/i&gt;&amp;quot; might work better.&lt;p&gt;That aside, would this method scale? 135,000 torrents doesn&amp;#x27;t seem comprehensive, so I would expect real world use to have many more. Maybe a different SQLite db for different categories?</text></comment>
<story><title>Database-less torrent website</title><url>https://boredcaveman.xyz/post/0x1_dbless-torrent-website.html</url></story><parent_chain></parent_chain><comment><author>lekevicius</author><text>One unmentioned con: no updates, no new torrents can be added (or, updates require re-deployment of full new .sqlite db, together with a new website). I think there&amp;#x27;s a space for decentralized database format. Something that would have immutable rows (not the whole db), ranges and search, indexes, etc. Maybe there&amp;#x27;s something like this already?</text></comment>