Right, and that's what we've been trying to encourage. The problem is when there are so many new users that the pre-existing culture is overwhelmed, which is why I think we should be careful. That's all.
I really doubt that will happen though with the invite system. Because of the system, it makes a voat/digg like exodus next to impossible. Even if the dump thread absolutely blows up (as in, gets on all or something), it would still keep the new members trickling rather than surging.
One thing that could be done is if there was a LB infront of a bunch of nodes. If the LB detects that you are a current member it sends it through to a bank of servers dedicated to existing members. That leaves non-existing members curiously looking at the front pages battle over a few servers that if they go down, it doesn't stop existing members from continuing to populate the site with content.
In saying that though, if the bottleneck is more the Databases that the front end nodes, then maybe look at replicating across a cluster of databases throwing non-members at specifically configured read focused databases rather than read/write.
I dunno some thoughts for keeping the site up for if we do get another hug of dead from Reddit Exodus 3: The Final Straw
Right, and that's what we've been trying to encourage. The problem is when there are so many new users that the pre-existing culture is overwhelmed, which is why I think we should be careful. That's all.
I really doubt that will happen though with the invite system. Because of the system, it makes a voat/digg like exodus next to impossible. Even if the dump thread absolutely blows up (as in, gets on all or something), it would still keep the new members trickling rather than surging.
One thing that could be done is if there was a LB infront of a bunch of nodes. If the LB detects that you are a current member it sends it through to a bank of servers dedicated to existing members. That leaves non-existing members curiously looking at the front pages battle over a few servers that if they go down, it doesn't stop existing members from continuing to populate the site with content.
In saying that though, if the bottleneck is more the Databases that the front end nodes, then maybe look at replicating across a cluster of databases throwing non-members at specifically configured read focused databases rather than read/write.
I dunno some thoughts for keeping the site up for if we do get another hug of dead from Reddit Exodus 3: The Final Straw