Transcription: a Twitter thread from Gary Bernhardt.

  • You, the one who is reading this! You don’t need Kubernetes!
  • Also microservices.
  • Also queues that are separate from your primary database (for most apps).
  • Google cosplay is not business-critical.

Source: https://twitter.com/garybernhardt/status/1344341213575483399

  • blotz@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    4 months ago

    xD just blocked the spammer and all his comments disappeared. Imagine working so hard to spam and it takes 2s to for someone to hide your posts.

  • 4am@lemm.ee
    link
    fedilink
    arrow-up
    0
    ·
    4 months ago

    Small app developers are all just temporarily embarrassed cloud service providers

  • Platypus@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    0
    ·
    4 months ago

    I’ve been migrating one of my company’s apps from microservices back to monolithic Java. It’s wonderful. I haven’t touched a line of yaml in weeks.

    • clif@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      4 months ago

      Currently migrating a massive monolithic Java application to microservices… The circle of life continues.

      Want to just swap jobs in ~5 years to keep the cycle going? You can migrate this project back to a Java monolith and I’ll migrate your monolith back to micros :D

      • SmoothLiquidation@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        4 months ago

        Honestly this just sounds like periodically refactoring everything to remove cruft can be a good thing. Also, it helps you understand how the existing code works if you change it and not break everything.

  • Justin@lemmy.jlh.name
    link
    fedilink
    English
    arrow-up
    0
    ·
    4 months ago

    I mean this is kind of bullshit. There’s a lot of things that run in containers these days, and kubernetes is the best way to run containers. If you can do everything with static js or managed services, more power to you, but as soon as you have multiple services talking to each other, you should be using kubernetes, and you should probably consider message queues.

    • dfyx@lemmy.helios42.de
      link
      fedilink
      arrow-up
      0
      ·
      4 months ago

      I never got into kubernetes but docker swarm mode services (not to be confused with old docker swarm) are pretty similar and they’re absolutely amazing for small deployments, even for just a home lab. If there’s anything I want to self-host, no matter if it’s homeassistant, jellyfin, nextcloud, a mastodon instance, a lemmy instance, GitLab or whatever, I can usually just get a preconfigured container, adjust some lines in a docker-compose.yml to fit my environment and be done with deployment in under 5 minutes without having to worry about dependencies, isolation or most configuration. Same for the stuff I write myself. Most of my stuff has a very simple GitLab CI config of maybe 20 lines and immediately shows up live when I merge my changes into main.