• recursed@lemmy.recursed.net
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    This made me chuckle for a good 10 minutes!

    At work we’re currently in the last layer of the iceberg with 35+ microservices, with ten different Kubernetes instances for different uses and a supported OnPrem version.

    It is bit of a learning curve and we definitely have two “mono-services” that we’re actively braking down due to it accumulating seven years worth of different ideas and implementations.

    I think currently I’m still heavily in favor in microservices in a project of our scale as it easily let’s us enhance, trash, or reimplement different areas of the app; but man is it a pain in the ass to manage sometimes 😂

    • RandomDevOpsDude@programming.devOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      I think we have ~400 microservices of varying types that deploy in many ways to many places (big proponents of using the right tools for the job rather than forcing preferred tools) and definitely in the last block. Although, as a DevOps guy my life would be a lot easier if we had a handful of monster monoliths, I understand it doesn’t make sense for our scale. I can fantasize though, and this meme hits extremely close to home 😅

      Tangentially, at my previous job we were in blocks 4 and 5 of transitioning away from a single monolith. Major issues arise when a “Java only shop for 20 years” start down this path with an extreme mindset of “we only use Java”. Java kubernetes controllers? lmfao, no thanks (they wanted them though 😑)