• bort
    link
    fedilink
    arrow-up
    15
    ·
    edit-2
    9 months ago

    I agree, that good cloud engineers can save costs in the cloud. But I also think good non-cloud engineers, can save much much more.

    When you are rewriting your entire stack to leverage cloud performance, you could probably spend a similar effort for a rewrite that increases regular performance by a similar factor.

    RE: Containers, even if you DO go that route…

    I was under the impression, that stateless stuff without containers requires a strong vendor login (aws lambda, google functions, azure function). Are you saying, I could do stateless without vendor-lockin and without containers and without kubernetes? This is news to me. Please point me to some resources

    • redcalcium@lemmy.institute
      link
      fedilink
      arrow-up
      2
      ·
      9 months ago

      These days there are many solutions to deploy kubernetes on a fleet of bare-metal servers, so if you use kubernetes, the option to take everything in house again is available. Distributed storage are the toughest one to setup in house but there are many mature solutions that integrate with kubernetes well these days.

      • bort
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        9 months ago

        is stateless possible without kubernetes? (and without vendor lock in?)

        GP said:

        RE: Containers, even if you DO go that route, do you really need Kubernetes, which will come at an additional monetary and also maintenance cost? The likely answer at least initially is a big fat “no”.

        • redcalcium@lemmy.institute
          link
          fedilink
          arrow-up
          2
          ·
          9 months ago

          There are self-hosted runtime such as workerd that allows you to run your own stateless lambda-like platform. It’s kinda losing steam these days though, and everyone seems to be pushing self-hosted kubernetes as the best way to get off the cloud these days.