1. 7
  1.  

  2. 3

    Not the worst article, although the tone might rub people the wrong way.

    It is well-worth, again, clicking through to the article he mentions: Kelsey Hightower’s https://changelog.com/posts/monoliths-are-the-future - which was featured on this site already, I believe.

    Personally, Hightower’s article couldn’t have landed in my lap at a better time.

    Both articles paint the picture of an individual that could become caught up in all the hype, money, spending, and new hiring that the “latest thing,” brings - and that person is my manager.

    I’m still struggling how to handle telling him in better words that he’s pushing us in the wrong direction, finger endlessly spamming the trigger of the gun stuck to his shoe.

    And figuring out how to be the manager that should be to my peers, who need some guidance in all the areas of discipline and software engineering.

    1. 2

      The language is confrontational, but what else would work?

      So many developers are absolutely, dogmatically convinced that a microservice architecture is simpler because the individual components are separated out.

      But a network call is not simpler than a functional call. It just isn’t.

      What other approach could be used to show people that they are just wrong?

      1. 3

        The author is notorious for hyperbole, but I agree in this case it feels right. It’s jarring, like pulling a fire alarm. But sometimes you need that.

        1. 2

          Some luminary I follow on Twitter (I forgot which one) recently said something along the lines of: if you do the preparatory work in your codebase to be able to spin out a microservice, you’ve already achieved most of the benefits. To which I mentally added: while not incurring any of the costs and retaining the ability to easily refactor and correct mistakes.