Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Microservices – State of Developer Ecosystem 2022 (JetBrains)

jetbrains.com

Post reply on HN
Print view View original

31–40 of 47 posts

Re: Microservices – State of Developer Ecosystem 2022 (JetBrains)

#31

Post by corpMaverick »

geodel wrote: post #23
corpMaverick wrote: post #10

Earlier quoted context omitted.

> Microservices can be done right - but then they're just Service Oriented Architecture. True. > As a concept, they have been one of the most toxic concepts to be released on the tech world. Sadly, I have to agree. One of the problems is that people assume that Microservices "should be as small as possible" when they should be "Small enough that a small team can own them" > I've seen literal devastation in multiple c…

> One of the problems is that people assume that Microservices "should be as small as possible" when they should be "Small enough that a small team can own them" I don't know what people should do. It is named as micro service after all. It is same with Agile cult with endless sprints, stories, epics, sagas, daily scrums, scrum of scrums, scrum master of ceremonies, and what not, people are then told "Do what works i…

> I don't know what people should do. It is named as micro service after all.

Totally agree.

They are "micro" only from the point of view of a company that has an application with millions of LOCs and thousands of developers working on it.

Re: Microservices – State of Developer Ecosystem 2022 (JetBrains)

#32

Post by zo1 »

dboreham wrote: post #19
jugg1es wrote: post #17

Earlier quoted context omitted.

> Microservices can be done right - but then they're just Service Oriented Architecture. Thanks for saying this out loud.

Silly me always thought Microservices was just a new word for SOA. What was the difference supposed to be?

You've then been fortunate enough to have never worked at a place where something simple like a "join" requires a call to a separate service.

Suddenly something trivial becomes buzzword-filled chaos. Observability, apm, monitoring, kubernetes, scaling, events, pub sub, api contracts, Kafka, streams, multi repos, build pipelines, github workers, eventual consistency and so on.

Re: Microservices – State of Developer Ecosystem 2022 (JetBrains)

#33

Post by jugg1es »

dboreham wrote: post #19
jugg1es wrote: post #17

Earlier quoted context omitted.

> Microservices can be done right - but then they're just Service Oriented Architecture. Thanks for saying this out loud.

Silly me always thought Microservices was just a new word for SOA. What was the difference supposed to be?

a capital 'M' microservice is a service that is entirely self-contained with its own datastore and everything. It's an architecture that makes sense if you are talking about the 'Orders' component of an e-commerce website but starts to get really weird if you need to share any kind of data between the microservices.

Re: Microservices – State of Developer Ecosystem 2022 (JetBrains)

#34

Post by baz00 »

yakshaving_jgt wrote: post #25
geodel wrote: post #20

Earlier quoted context omitted.

> Do we really want another religious war over microservices vs monoliths? I guess not since microsevices have won already.

I must have missed that award ceremony.

Just look for the smears of shit over everything. They're over there.

Re: Microservices – State of Developer Ecosystem 2022 (JetBrains)

#35

Post by baz00 »

simmerup wrote: post #27
baz00 wrote: post #6

Earlier quoted context omitted.

I'm taking time out of the industry and doing other stuff. When it finally works out that it's not a viable approach for perhaps 90% of the products out there I'm going to come back and sell exit strategies.

Take time out and you may risk getting left behind on the likely shift to AI augmented coding

A monkey could work that out in thirty minutes.

Re: Microservices – State of Developer Ecosystem 2022 (JetBrains)

#36

Post by rozap »

willsmith72 wrote: post #22
geodel wrote: post #20

Earlier quoted context omitted.

> Do we really want another religious war over microservices vs monoliths? I guess not since microsevices have won already.

From where I stand it's the opposite. 5 years ago microservices were cool, now it's just the banks and telecomms adopting them, while the others realise sometimes they're useful, sometimes a monolith is useful, sometimes a service-oriented architecture (not micro) is useful.

Yea, I think they "won" out in the discourse over the last ~5 years, but I'm convinced it was another ZIRP phenomenon that will quickly fade as belts get tightened. When money rains down like mana from the heavens, sure, go ahead and hire half a dozen Ops folks to run your big ball of mud that maxes out at 8 req/s and has a 6 figure monthly AWS spend. I think things are going to swing back the other way, purely because efficiency will more important than it was over the last decade.

Re: Microservices – State of Developer Ecosystem 2022 (JetBrains)

#37

Post by PH95VuimJjqBqy »

miroljub wrote: post #29
PH95VuimJjqBqy wrote: post #13

Earlier quoted context omitted.

SOA is a specific architecture, not a generic pattern name. It implies things such as an ESB, etc. microservice is a distinct architecture.

You can do SOA without an ESB. You don't have to use ESB everywhere to have SOA architecture.

That's true but SOA without an ESB is a very small solution. As that solution grows an ESB will be created whether or not the team thinks of it as an ESB.

Re: Microservices – State of Developer Ecosystem 2022 (JetBrains)

#38

Post by quinnirill »

jokethrowaway wrote: post #7

Microservices can be done right - but then they're just Service Oriented Architecture. As a concept, they have been one of the most toxic concepts to be released on the tech world. I remember a conference where some influential person had a slide "if your service doesn't fit on a slide, it's too big". I've seen literal devastation in multiple companies coming from inept technical leaders who drank the microservices k…

Yep, it can be done right. I’ve been in a team where we had more services than people yet most of the services were just chugging along with little to no maintenance (thanks to most being in a monorepo with few dependencies so the spam of dependencies getting out of date was manageable).

It was a constant uphill battle though, my time was largely spent on trying to prevent the creep of services born out of trying to enforce Conway’s law rather than to contain it’s impact. When people put in the effort of shaping the team/organization around the most optimal architecture rather than shaping out the architecture to fit the organization, it works out rather nicely and yields good productivity and an efficient system. Luckily at the time even ICs like me had enough sway to keep things at check.

Re: Microservices – State of Developer Ecosystem 2022 (JetBrains)

#40

Post by [deleted] »

selcuka wrote: post #3
cinbun8 wrote: post #2

This is a sub-section of the survey, shown only to people who responded with `Yes` to the `Do you develop microservices?` question. I still don't understand how 19% of respondents picked 'Monolith' as a system design approach. Perhaps they coexist?

The percentages don't add up to 100%. Multiple answers were allowed, so it is possible that one developer works on both monolithic and microservice based projects.

[deleted]
Post reply on HN