News for hackers. Stuff that matters.
Re:Honest Microservices by sdevonoes on Friday March 26, 2021 @08:58AM (#26591559)
I agree, but I think the author is missing one big point:

- microservices is not a tech concept, it's a management concept

We (devs) like to think that microservices is all about tech, but in reality it's a disguised tech concept used by management to:

- grow the team. We are going to need more devs to build more microservices!

- have more things to manage. Like, do you really think managers want to say "yeah, I manage the delivery of... a library". At the end of the quarter they want to say: "yeah, I manage the delivery of a service that..."

- get salary raises. See previous point

That's it. The tech industry is shifting (has shifted already?) from a "tech people know better. Let them drive the big decisions" perspective to a "lean managers drive tech decisions because they know Agile and Agile is good" one.

Microservices is all about management/organizational topics, not about tech.

Re:Honest Microservices by candiddevmike on Friday March 26, 2021 @09:27AM (#26591857)
I don't know why this post has so many downvotes. Kingdom building has come to developer teams. You no longer see large dev teams that collaborate really well, instead you see silos and pizza teams. No one talks, everything becomes a political turf war, and the end result is everyone taking their ball and going home. Higher ups don't understand the complexity of the stack, they just hear we're constantly shipping new things--that has to be good? New is better than maintenance right?

Microservices are just managers codifying the boundaries of their kingdom.

Re:Honest Microservices by pydry on Friday March 26, 2021 @10:43AM (#26592739)
It's hardly accurate to say it's come to developer teams - it's always been like this. This is simply human nature manifested in large groups.

Large groups operating well together without clearly defined boundaries of responsibility is very much the exception rather than the norm and always has been.

Re:Honest Microservices by candiddevmike on Friday March 26, 2021 @10:52AM (#26592857)
I would argue that a lot of the "famed agility" and effectiveness of startups is their flat structure and lack of middle management bloat, especially for the devs. As soon as you start splitting the dev teams apart, productivity grinds to a halt and you start hearing phrases like "this team owns that" and other territory marking behavior.
Re:Honest Microservices by pydry on Friday March 26, 2021 @11:07AM (#26593026)
I think that well defined software teams that can integrate effectively with one another in large companies could spell the end of software startups.

The dysfunctionality of middle management outweighed economies of scale for a long time but I doubt it will last forever.

Re:Honest Microservices by jonfw on Friday March 26, 2021 @11:10AM (#26593072)
That's probably because startups are small organizations. Nobody is arguing that productivity increases linearly as you add 2 pizza teams. Productivity increases logarithmically. '2 pizza teams' are supposed to represent where the productivity gains of adding a dev to a team are marginal.
Re:Honest Microservices by ryanbrunner on Friday March 26, 2021 @09:07AM (#26591652)
In my experience, engineers will be pushing for microservices as often if not more than tech management. The reasons are sometimes different - a lot of times it reduces down to "our existing services are all written with old, unsexy technology and I want to do something greenfields with new tech that looks good on my resume", but they're definitely not fighting against the tide of management insisting on microservices.
Re:Honest Microservices by devonkim on Friday March 26, 2021 @09:55AM (#26592157)
Another reason I’ve seen is “this project will be around for a while and we should skip past the growing pains to go into microservices.” If it’s a rewrite of an existing system, then it’s more justifiable because it’s about eliminating technical debt and is not a greenfield project. But for new efforts where an organization has never seen customer demand in X, Y, Z services being created it’s pure conjecture and premature optimization to essential refactor across service boundaries before a monolith with some usage metrics even exists
Re:Honest Microservices by sdevonoes on Friday March 26, 2021 @09:10AM (#26591681)
I see that as well, but only if microservices have been already "approved" in your organization (usually by upper tech management).
Re:Honest Microservices by robertjp on Friday March 26, 2021 @09:53AM (#26592141)
It's definitely a tech thing if you "need" the resource scalability. All it takes in certain types of work. If a customer can click a button and that ends up allocating a gig of memory or using 5 minutes of CPU, then scaling out is the only reasonable option.
Re:Honest Microservices by sdevonoes on Friday March 26, 2021 @10:21AM (#26592485)
Agree. But this is true only for a very few of the tech companies out there.
Re:Honest Microservices by 100011_100001 on Friday March 26, 2021 @09:10AM (#26591683)
I disagree. It appears that you are dealing with bad management. Most Business people think in terms of features and defects. In most cases they don't even know what microservice does what, they probably don't even know the names of most microservices.

I consider microservices a natural extension of OOP on a service level. Each microservice functions like an abstract object that represents a thing. Of course it has the same drawback as OOP, do it too much, or implement it too little and you got problems.

Re:Honest Microservices by 100011_100001 on Friday March 26, 2021 @12:13PM (#26593818)
I am perplexed by the downvotes. Which part of my statement is "wrong" enough to get downvotes? I am trying to understand if I have an opinion that's incorrect, or that people don't like it?
Re:Honest Microservices by jayd16 on Friday March 26, 2021 @01:55PM (#26594972)
Striping your objects across processes and machines is a very different set of problems than OOP.

But even ignoring that, you fail to see that OOP is also a form of management concept. Its still compartmentalization and abstraction such that no developer must understand the full state of the system to make sense of an api.

OOP is much more a huaman management and communication concept than a technical one.