• BearOfaTime@lemm.ee
    link
    fedilink
    English
    arrow-up
    17
    arrow-down
    4
    ·
    6 months ago

    This is a “one of a kind” error.

    OK, that it can happen at all is a problem. And sorry, but the idiots who put their data in with Google should be fired.

    I get offloading risk, little good will that do when your company goes tits up.

    • slimarev92@lemmy.world
      link
      fedilink
      English
      arrow-up
      8
      arrow-down
      1
      ·
      6 months ago

      Where would you put their data then? Self hosting is not exactly safe either.

      At the end of the day, every approach has its tradeoffs. Using a reputable cloud provider is a very valid choice.

      • whats_all_this_then@programming.dev
        link
        fedilink
        English
        arrow-up
        9
        arrow-down
        1
        ·
        6 months ago

        Thank you! Every time a story like this comes up, people seem to wanna pretend managing your own hardware is all sunshine and rainbows. Especially if you want global scale or as little down-time as possible, cloud provider’s your best bet, albeit one where you have less control than you would with your own servers.

        Opinion: You should be building on top of open source platforms and tools (Docker, Kubernetes if you need it…granted I’m not an expert in this area) to mitigate some of the vendor-lockin, and take a multi-cloud approach. If you’re mainly hosting on GCP for example, host smaller deployments on AWS, Azure, Cloudflare, or something else as a contingency…eventuality you can also add or just move to your own servers relatively painlessly. Also AGGRESSIVELY backup up your database in multiple places.