This is an opportunity for any users, server admins, or interested third parties to ask anything they’d like to @nutomic@lemmy.ml and I about Lemmy. This includes its development and future, as well as wider issues relevant to the social media landscape today.
Note: This will be the thread tmrw, so you can use this thread to ask and vote on questions beforehand.
Is there any limitations with the database (postgres)?. I know postgres is one of the best (maybe even best) monolith database (running on one node) at the moment, but will the space be enough? With this in mind, has there been any consideration of migrating to a distributed database like ScyllaDB or CassanraDB to alleviate potential space constraints? On the other hand, if Lemmy doesn’t intend to store data for long periods, maybe the capacity of Postgres would suffice. Any thoughts or plans on this? I appreciate your insights on this matter.
Disk space is definitely not an issue for us w/ postgres, or any text data really. The entire wikipedia english text data, is ~20GB. Images are the main disk-space concern for servers.
A backup of lemmy.ml’s DB is only ~1.8 GB currently, and that’s 3+ years of data.
We have no plans to move away from postgres, and lose all of its features and performance.
It may be a stupid question(, i hope so), but after taking a look at your Json(, not sure if that’s the correct term), i’ve seen that a post with an image will have in the “post”(, not “posts”,) node two u.r.l.s. for the picture, one under “url”, and the other under “thumbnail_url”. Since both u.r.l.s are different, i sure hope it doesn’t lead to almost twice as much storage, probably not 🤷♂️
> ScyllaDB or CassanraDB
Distributed columnar databases are a different breed, migrating to that would not be trivial as it comes with a reduction of features compared to a traditional SQL databases, such as partial SQL support, bad join performances and lack of secondary indexes.