It was to talk about “team restructuring”

  • @severien
    link
    5
    edit-2
    9 months ago

    Being cloud-agnostic also means additional cost/complexity.

    Sometimes the only way to win the game is by not playing it.

    • @MrPoopyButthole
      link
      English
      89 months ago

      I would argue that most cloud native services existed in their standalone forms way before public clouds made their own versions. For example there are loads of message queue systems that are just as easy to incorporate and are cloud agnostic, some of them are FOSS. Sure you can reinvent the wheel but in most cases something like RabbitMQ will work OK depending on the use case. Having cloud vendor lock in is where cost catches up with you. Complexity is arbitrary since there are ways to make anything overcomplicated.

      • @severien
        link
        2
        edit-2
        9 months ago

        RabbitMQ is more expensive on AWS than e.g. SNS/SQS. It’s not a coincidence, you’re trading lock-in for a cheaper price.

        The increased complexity comes from the fact you will need some components which exist in either managed, but vendor lock-in form, or you need to spin them up / managed yourself.

        • @MrPoopyButthole
          link
          English
          39 months ago

          Right, paying for managed services whether cloud native or not is pretty much the same thing, it hurts in the pocket. Spinning up your own RabbitMQ on a VM is both cheap and cloud agnostic, especially if sized right.