me is me@lemmy.ml to Lemmy@lemmy.ml · 2 years agoLemmy is blowing uplemmy.mlimagemessage-square203linkfedilinkarrow-up1492arrow-down13file-text
arrow-up1489arrow-down1imageLemmy is blowing uplemmy.mlme is me@lemmy.ml to Lemmy@lemmy.ml · 2 years agomessage-square203linkfedilinkfile-text
minus-squarejbenguira@lemmy-u3.vm.elestio.applinkfedilinkarrow-up5arrow-down1·2 years agoI think we really need to address the scaling issue, one option could be to use clichhouse instead of postgres
minus-squarehglman@lemmy.mllinkfedilinkarrow-up2·2 years agoThats certainly not the right kida of storage system for a site like this.
minus-square777@lemmy.mllinkfedilinkarrow-up1·2 years agoI 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.
I think we really need to address the scaling issue, one option could be to use clichhouse instead of postgres
This gives me MongoDB flashbacks
Thats certainly not the right kida of storage system for a site like this.
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.