aleixmorgadas’s avataraleixmorgadas’s Twitter Archive—№ 1,173

  1. …in reply to @gorkaio
    @gorkaio Exactly! I think it should be a contraction in the number of services. Today, we have almost 1 service for every 2 developers I would say that's partially a legacy or there are several that have been deprecated but unable to shut them down
    On twitter.com Twitter logo aleixmorgadas’s avatar Mood -2 🙁
    1. …in reply to @aleixmorgadas
      @gorkaio In a rapid scaling organization, we got plenty of patterns for growth. Either for systems or per team. Divide pattern, Split pattern, ... Yet, it might make sense when you're learning about the domain, and it's easier to experiment in a new area.
      Permalink On twitter.com Twitter logo aleixmorgadas’s avatar Mood +2 🙂
      1. …in reply to @aleixmorgadas
        @gorkaio Still, I'm missing that, when you learn about the domain, able to capture that knowledge and represent it in the services. Sometimes happens, that you split into two services something that shouldn't be split and you figure it out later
        Permalink On twitter.com Twitter logo aleixmorgadas’s avatar Mood -2 🙁
        1. …in reply to @aleixmorgadas
          @gorkaio The effort of merging: - Code - Infra - Redirect the traffic on demand - Move the data/normalize it ... it's huge, and there are few tools that support that.
          Permalink On twitter.com Twitter logo aleixmorgadas’s avatar Mood +2 🙂
          1. …in reply to @aleixmorgadas
            @gorkaio I'm thinking about how @graalvm has enabled these merges to be possible even with multiple platforms/languages.
            Permalink On twitter.com Twitter logo aleixmorgadas’s avatar Mood 0