• Renacles@beehaw.org
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      1
      ·
      3 years ago

      It’s not so bad, microservices let’s you focus on your current task instead of having to deal with years upon years of legacy code every day.

      Microservices can get messy but they are much better than the alternative even if you aren’t looking at performance and scalability.

  • Derpgon@programming.dev
    link
    fedilink
    English
    arrow-up
    4
    ·
    3 years ago

    It’s always the full circle - from monolith, to micro services, then someone just copies the code back to the main repo, and we’re back to square one.

  • tyw0kki@programming.dev
    link
    fedilink
    English
    arrow-up
    3
    ·
    3 years ago

    Trying to do Postgresql TLS /w Internal PKI chain created by Cert-Manager made me want to throw my laptop out the window yesterday.

    This stuff is hard.

    • vapeloki@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      ·
      3 years ago

      Use a postgresql operator for that.

      How many postgresql databases without replication and backup if have seen … and 90% of then contained critical data.

      If you really need to run the db inside containers, never by hand.

      And as a full time postgresql dba: NEVER run your production databases inside k8s

  • marcos@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    3 years ago

    We are at layer 5 at work, blissfully ignoring anything deeper. What is quite the thing because microservices don’t become very useful until you reach layer 6.

    But well, I stopped advocating for consolidating most of the services a couple of years ago. AFAIK, we need some 3 large services and everything else should be a monolith.