News for hackers. Stuff that matters.
Re:You Want Modules, Not Microservices by pjmlp on Tuesday January 03, 2023 @10:03AM (#34232220)
Same thing with microservices, unless you do a blue green deployment, have a planned shutdown, load balancer in between releases,...
Re:You Want Modules, Not Microservices by regularfry on Tuesday January 03, 2023 @10:24AM (#34232521)
The key word is "independently".
Re:You Want Modules, Not Microservices by pjmlp on Tuesday January 03, 2023 @10:29AM (#34232607)
There is no independently in distributed systems.
Re:You Want Modules, Not Microservices by regularfry on Tuesday January 03, 2023 @10:37AM (#34232764)
You can't solve the halting problem either, and yet somehow useful work gets done.
Re:You Want Modules, Not Microservices by jacobr1 on Tuesday January 03, 2023 @11:01AM (#34233138)
But there are rules of blame.

With microservices, as long as you maintain the contract with caller services, you can deploy whenever you want. If you have some kind of issue, your team is solely responsible. If the caller services do weird things, they are responsible for fixing them.

If you are pushing changes to a module as part of a more monolithic, or wrapper service - if you do a deploy and break the whole big service, you are now responsible for the entirety of any issue, which is now more likely due to integration risk and unrelated changes from others, especially because now there need to be coordination across many teams integrating - hopefully via tests and observability. But this requires a high-degree of maturity for automated quality assurance and site reliability. If you don't have that, the operational risks are very high. So that alternative is having some ops-like function, or other integration team responsible. Or doing more top-down waterfall coordination.

Given the service maturity needed is rare, microservices distributes that operational ownership in a way where there is more accountability.

Re:You Want Modules, Not Microservices by pjmlp on Tuesday January 03, 2023 @11:30AM (#34233618)
Unless there is infrastructure in place good luck replicating those dropped requests as services are replaced.

Infrastructure that someone has to take care of.

Re:You Want Modules, Not Microservices by Pet_Ant on Wednesday January 04, 2023 @12:05PM (#34248216)
Every organisation I've worked at that had microservices has had all of them released every other Thursday at the same time by the same pipeline because they are tied to the organisation scrum schedule. Also, most changes are part of epics that span multiple microservices. If you are gonna argue that properly done microservices don't have that problem you are free to practice your perfect microservices alongside perfect scrum, oop, and communism.
Re:You Want Modules, Not Microservices by jacobr1 on Wednesday January 04, 2023 @02:22PM (#34250116)
I was arguing the opposite, coordinated deployments already presumes more maturity than I was considering. I've only been at one company with same-day deployments. All the other places have been free-for-alls where each group determines their own release schedule, with their own pipelines. Managing deployments between dependent services thus requires significant coordination overhead (or none, because you are stuck with what you get until the other teams deliver your needs on their own timeline).

In chaotic environments like that, microservices help with defining clear ownership of operational responsibility, though at the cost of clear responsibility for the overall distributed system. This comes at the cost of making it hard to develop, let alone ship, changes that impact multiple microservices (outside the scope of a single team, or closely related sibling teams).

The main point I was making was that, with a more monolithic system, managing that kind to organization disfunction, necessitates top-down, waterfall like control. So moving to microservices enables non-coordinated agility removing one layer of coordination problem (a the cost of other problems).