• peoplebeproblems@midwest.social
    link
    fedilink
    English
    arrow-up
    15
    ·
    10 hours ago

    You know, this really has me pondering my projects architecture. We have tiers of services.

    At the top, we have the UI. Then we have a “consumer” an “orchestra” and a “data” tier.

    Data is the tier that exclusively talks to databases. Orchestra talks to the multiple data services. A good chunk of business logic is here. Consumer uses the orchestra and handles UI requests.

    All it essentially does is split the monolith into 3 services at minimum. And since it’s on the cloud, there’s a start up cost where we need to spin up 3 machines instead of whatever you can do with microservices. What benefit do I get?

    • adminofoz@lemmy.cafe
      link
      fedilink
      English
      arrow-up
      4
      ·
      edit-2
      4 hours ago

      Separation of concerns is a major benefit that shouldn’t be overlooked with security implications. Assuming you are properly restricting access to each worker node / “tier”, when one tier inevitably becomes compromised; it doesn’t result in the complete compromise of the entire monolith.

    • NewDark@lemmings.world
      link
      fedilink
      arrow-up
      4
      ·
      7 hours ago

      If you aren’t a gigantic company with so many moving parts it would make your head spin… Probably not much? There is a benefit where you can individually scale your services based on need but that feels like overkill for most.