I hope this won’t be counted as some form of self-promotion, even though I am sharing a post from my own blog.

As a tech worker who works in a Cloud shop, I wanted to elaborate the many reasons why I find working with Clouds terrible, from multiple points of view.

I tried to organize my thoughts in a (relatively long) post, in which both technical aspects and political aspects (which are very related) are covered.

I am sure many people will have different perspectives, and this could be potentially also a nice prompt for a discussion.

  • loudwhisper@infosec.pubOP
    link
    fedilink
    English
    arrow-up
    0
    ·
    5 months ago

    Is that what you get with Cloud? Because there are still a million ways to shoot yourself in the foot. The main difference is that the single genius doesn’t need to implement things him/herself, but decisions still need to be taken and fragile setups can still be built.

    Imagine an ec2 instance in a satellite account performing some business critical function with an instance role, whose custom IAM policy allows to do it in another account. Clouds are not giving you good engineering, they are giving you premade building blocks, you can absolutely still make a mess with those. Even more, the complexity and the immense portfolio of features can allow very creative ways to build very low-quality systems.

    I think you can have good, boring, simple systems built by engineers. With or without Cloud services.

    • Tja@programming.dev
      link
      fedilink
      English
      arrow-up
      0
      ·
      5 months ago

      You can still make a mess, but you can’t fuck up the building blocks, so it’s a big improvement.

      Using an ec2 instance is already a yellow flag, you have higher level services for most tasks.