4

Folks are bragging about having 99 microservices. I don't know for what joy folks create that much microservices. They may have their own reason. I'm trying to understand what is the workflow for small companies with few microservices. Could anyone shed some light? I'm thinking of building orchestrator where I don't have fancy features like k8s and get the basic job done. Focused more on simplicity and UX.

Comments
  • 2
    Microservices only make sense on larger scale imo.

    Small to medium I'd say majestic monoliths all the way.
    Might do a headless front-end & API, if there's interest in a mobile app or the customer expects / needs the additional sparkles :)
  • 3
    The people who decide where the data goes are not motivated by anything sane.

    So these companies end up with data/assets scattered all the fuck over the cloud.

    Hence, microservices.
  • 1
    @HiFiWiFiSciFi they're none the wiser and blinded by that shiny ☁️ over there.
  • 0
    Just use celery with redis, or something like it in another language. Run everything including celery workers with systemd. And when it is time to scale out, just build a single docker image and run it in k8s with a autoscaler.
Add Comment