649
Lemmy is blowing up
(lemmy.ml)
How do you feel about the massive influx of users?
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 10 Jun 2023
649 points (99.2% liked)
Lemmy
11948 readers
1 users here now
Everything about Lemmy; bugs, gripes, praises, and advocacy.
For discussion about the lemmy.ml instance, go to !meta@lemmy.ml.
founded 4 years ago
MODERATORS
I think we really need to address the scaling issue, one option could be to use clichhouse instead of postgres
I think probably a pluggable storage backend is the best move. For example, any cloud hosted instance could use a native document storage format such as dynamodb, which is often quite cheap or free for small use-cases.
Bit of a pain to store in Dynamo, though. You'd need to write a bunch of different views, I think.
One comment thread makes sense as a partition, but listing threads is going to be awkward, and search is basically a no-no.
Not necessarily a pain, you just have to model the data very differently in something like DynamoDB. Those views are secondary indexes.
Search, though, you're right. You'd be running ElasticSearch along side it and the cost and complexity starts to go up. Or just abandon having a functional search entirely, like Reddit did...
This gives me MongoDB flashbacks. Postgres, if properly set up, should easily handle thousands of users.
Thats certainly not the right kida of storage system for a site like this.
Indeed PostgreSQL is not designed for large scale horizontal sharding with eventual consistency. Also ClickHouse is designed for OLAP workloads likely making it even less suitable.