Lemmy

2172 readers

1 users here now

Everything about Lemmy; bugs, gripes, praises, and advocacy.

For discussion about the lemmy.ml instance, go to [email protected].

founded 4 years ago

MODERATORS

[email protected]

182

What is the long-term storage plan for Lemmy instances? (self.lemmy)

submitted 1 year ago* (last edited 1 year ago) by Kalcifer to c/[email protected]

82 comments fedilink hide all child comments

Over time, Lemmy instances are going to keep aquiring more, and more data. Even if, in the best case, they are not caching content and they are just storing the data posted to communities local to the server, there will still be a virtually limitless growth in server storage requirements. Eventually, it may get to a point where it is no longer economically feesible to host all of the infrastructure to keep expanding the server's storage. What happens at this point? Will servers begin to periodically purge old content? I have concerns that there will be a permanent horizon (as Lemmy becomes more popular, the rate of growth in storage requirements will also increase, thereby reducing the distance to this horizon) over which old -- and still very useful -- data will cease to exist. Is there any plan to archive this old data?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 3 points 1 year ago

AWS Postgres instances aren't that expensive, and they handle upgrades and backups for you.

That said, I'm interested in distributed storage, and maybe this fall/winter when I get some time off I'll try making a lemmy fork that's based on a distributed hash table. There are going to be a ton of issues (i.e. data will be immutable), but I have a few ideas on how to mitigate most of the issues I know about.