Usually no
You want microservices, but do you need them?
11–20 of 151 posts
Re: You want microservices, but do you need them?
#12microservices were an effect of the ZIRP era. you literally have places like Monzo bragging that they've 3 microservices for each engineer. 3 tier architecture proves time and time again to be robust for most workloads.
1 micro-service per pizza sized team seems to work pretty well.
Put it into a monorepo so the other teams have visibility in what is going on and can create PRs if needed.
Re: You want microservices, but do you need them?
#13On the theme of several other responders:
I don't want microservices; I want an executable. Memory is shared directly, and the IDE and compiler know about the whole system by virtue of it being integrated.
Re: You want microservices, but do you need them?
#14in my opinion "you need microservices" peaked around 2018-2019 ... does nowadays someone think that, apart from when you reach certain limits and specific contexts, they are a good idea?
Re: You want microservices, but do you need them?
#15We've removed/merged most of the unnecessary services. The ones left have operational needs to stay separate.
The current hell is x years of undisciplined (in terms of perf and cost) new ORM code being deployed (SQLAlchemy). We do an insane number of read queries per second relative to our usage.
I honestly think the newish devs we have hired don't understand SQL at all. They seem to think of it as some arcane low level thing people used in the 80s/90s.
Re: You want microservices, but do you need them?
#16I would really like to send this article out to all the developers in my small company (only 120+ people, about 40 dev & test) but the political path has been chosen and the new shiny tech has people entranced.
What we do (physics simulation software) doesn’t need all the complexity (in my option as a long time software developer & tester) and software engineering knowledge that splitting stuff into micro services require.
Only have as much complexity as you absolutely need, the old saying “Keep it simple, stupid” still has a lot of truth.
But the path is set, so I’ll just do my best as an individual contributor for the company and the clients who I work with.
Re: You want microservices, but do you need them?
#17I would really like to send this article out to all the developers in my small company (only 120+ people, about 40 dev & test) but the political path has been chosen and the new shiny tech has people entranced. What we do (physics simulation software) doesn’t need all the complexity (in my option as a long time software developer & tester) and software engineering knowledge that splitting stuff into micro services re…
I thought microservices were old by now, which is why this kind of articles are finally appearing.
Re: You want microservices, but do you need them?
#18microservices were an effect of the ZIRP era. you literally have places like Monzo bragging that they've 3 microservices for each engineer. 3 tier architecture proves time and time again to be robust for most workloads.
1 micro-service per pizza sized team seems to work pretty well. Put it into a monorepo so the other teams have visibility in what is going on and can create PRs if needed.
Uh? You eat less than a pizza per person?
Re: You want microservices, but do you need them?
#19I don't want microservices! What I want is a lightweight infrastructure for macro-services. I want something to handle the user and machine-to-machine authentication (and maybe authorization). I don't WANT the usual K8s virtual network for that, just an easy-to-use module inside the service itself. You should be able to spin up everything localy in a docker-compose container.
> What I want is a lightweight infrastructure for macro-services. I want something to handle the user and machine-to-machine authentication (and maybe authorization).
> I don't WANT the usual K8s virtual network for that, just an easy-to-use module inside the service itself.
K8s makes sense if you have a dedicated team (or atleast engineer) and if you really need need the advanced stuff (blue/green deployments, scaling, etc). Once it's properly setup it's actually a very pleasant platform.
If you don't need that Docker (or preferable Podman) is indeed the way to go. You can actually go quite far with a VPS or a dedicated server these day. By the time you outgrow the most expensive server you can (reasonable) buy you can probably afford the staff to roll out a "big boy" infrastructure.
Re: You want microservices, but do you need them?
#20The one thing I would like to preserve from microservices is stuff about database table hygiene. Large, shared database tables have been a huge issue in the last few jobs that I have had, and they are incredibly labor intensive to fix.
I feel that if you have multiple sets of application logic that need to access the same data, there should be an internal API between them and the database that keeps that access to spec.
Only allow clients to execute stored procedures?