With forewarning about a huge influx of users, you know Lemmy.ml will go down. Even if people go to https://join-lemmy.org/instances and disperse among the great instances there, the servers will go down.

Ruqqus had this issue too. Every time there was a mass exodus from Reddit, Ruqqus would go down, and hardly reap the rewards.

Even if it’s not sustainable, just for one month, I’d like to see Lemmy.ml drastically boost their server power. If we can raise money as a community, what kind of server could we get for 100$? 500$? 1,000$?

  • nutomic@lemmy.mlM
    link
    fedilink
    arrow-up
    9
    ·
    2 years ago

    Can we replace Lemmy.ml with Join-lemmy.org when Lemmy.ml is overloaded/down?

    I dont think so, when the site is overloaded then clients cant reach it at all.

    Does LemmyNet have any plans on being Kubernetes (or similar horizontal scaling techniques) compatible?

    It should be compatible if someone sets it up.

    • Leigh@lemmy.ml
      link
      fedilink
      arrow-up
      9
      ·
      2 years ago

      You could configure something like a Cloudflare worker to throw up a page directing users elsewhere whenever healthchecks failed.

      • nutomic@lemmy.mlM
        link
        fedilink
        arrow-up
        21
        arrow-down
        2
        ·
        2 years ago

        Then cloudflare would be able to spy on all the traffic so thats not an option.

        • Leigh@lemmy.ml
          link
          fedilink
          arrow-up
          14
          arrow-down
          6
          ·
          2 years ago

          spy on all the traffic

          That’s…not how things work. Everyone has their philosophical opinions so I won’t attempt to argue the point, but if you want to handle scale and distribution, you’re going to have to start thinking differently, otherwise you’re going to fail when load starts to really increase.

        • wagesof@links.wageoffsite.com
          link
          fedilink
          arrow-up
          4
          ·
          2 years ago

          You could run an interstitial proxy yourself with a little health checking. The server itself doesn’t die, just the webapp/db. nginx could be stuck on there (if it’s not already there) with a temp redirect if the site is timing out.