• jol@discuss.tchncs.de
    link
    fedilink
    arrow-up
    1
    ·
    6 months ago

    And the dev experience IMO is much better. I don’t have to deploy a huge ass service to test a tiny feature.

    • ☆ Yσɠƚԋσʂ ☆@lemmy.ml
      link
      fedilink
      arrow-up
      3
      arrow-down
      3
      ·
      6 months ago

      If you have to deploy your service to test features instead of being able to test them locally while developing them then you have a really poor dev workflow.

      • jol@discuss.tchncs.de
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        6 months ago

        If you don’t have a staging environment for doing integration testing of your feature in a non dev environment, you have a poor dev workflow. I never said I don’t test locally. And even then, I don’t want to run a huge monolith in my local environment if I don’t work with 90% of it.

        • ☆ Yσɠƚԋσʂ ☆@lemmy.ml
          link
          fedilink
          arrow-up
          2
          arrow-down
          2
          ·
          6 months ago

          Nowhere did I say you shouldn’t have a staging environment. However, if you can develop and test changes locally then by the time it goes to staging, the code should already be in good shape most of the time. Staging is like your guardrail, it shouldn’t be part of your main dev loop.

          Meanwhile, not sure what the issue is with running a monolith locally. The reality is that even large applications aren’t actually that big in absolute terms. Having to run a bunch of services locally to test things end to end is certainly not any easier either.