• NovaPrime@lemmy.ml
      link
      fedilink
      arrow-up
      0
      ·
      1 month ago

      A properly architected and implemented microservice architecture optimizes work throughput while minimizing risk. In practice its architecting in such a way that no part can take down the whole individually - the very opposite of a monolith where everything is inseparably interdependent at some level.

      Problem is, most organizations don’t know how to properly architect for and integrate microservice architectures into their environments and work process. Most think that a crew of former sysadmins can just spin up a few saas services, slap some autoscaling on it if they’re feeling spicy, segment along traditional monolith “frontend/backend” lines for “security,” and call it a day. They then spend time and money learning and/or fighting this system, only to see minimal (if any) improvement in work capacity/quality and instead end up with an outsized cloud bill.

      • frezik@midwest.social
        link
        fedilink
        arrow-up
        0
        ·
        1 month ago

        Problem is, most organizations don’t know how to properly architect for and integrate microservice architectures into their environments and work process.

        Which is exactly the same thing said about OOP, or structured programming, or Agile, or a number of other paradigms. Organizations aren’t doing it right, but it works if it’s “properly architected”. Yet, this “proper architecture” doesn’t seem to exist anywhere in the real world.

        In fact, I’ve argued before that if OOP is fundamentally about objects ending messages to each other, then microarchitectures are just an approach to OOP where the communication channel is over network sockets.

        If you understand things like encapsulation and message passing, then the difference doesn’t come down to microarchitecture vs monolith. It’s self-contained components vs not, and the method of passing messages is only important from a feasibility and performance standpoint.

    • ramble81@lemm.ee
      link
      fedilink
      arrow-up
      0
      ·
      1 month ago

      My favorite is seeing developers directly reach out to a DB of another microservice because “it’s just easier to pull the data from there”. One of the few times I’ve literally said “bruh”