Thinking of canceling Disney+? You’re not alone—after Jimmy Kimmel’s suspension, so many people rushed to quit that the cancellation page itself started crashing.

cross-posted from: https://lemmy.nz/post/28397398

The suspension triggered strong responses across social media and beyond. Hashtags like #CancelDisneyPlus and #CancelHulu trended as users shared screenshots of their canceled subscriptions.

With cancellations surging, many subscribers reported technical issues. On Reddit’s r/Fauxmoi, one post read, “The page to cancel your Hulu/Disney+ subscription keeps crashing.”

  • BCsven@lemmy.caEnglish
    1·
    23 hours ago

    Caching servers, they self replicate when a change is committed, then send back a signal to main server that task has completed

      • BCsven@lemmy.caEnglish
        1·
        19 hours ago

        Oh right, I skipped a part. It is not really a dev complexity prep issue. You build the database that serves the comments etc in as of in one place, then you deploy cache servers for scaling. They self replicate, so a comment in California gets commited to the dbase, the server in new York pulls the info over from the Cali change, it sends back that it is synced with the change. And vice versa. The caching servers do the work, not your program.

        • DreamlandLividity@lemmy.worldEnglish
          1·
          11 hours ago

          That entirely depends on your application. What you described is one possible approach, that will only work in specific circumstances.

          • BCsven@lemmy.caEnglish
            1·
            6 hours ago

            Besides application specifics, its how the internet works currently to give low latency. AWS, Azure, Linode etc have data centers across the globe to replicate data near where the people are.