I'm shocked Java is the most popular language. I thought it was primarily a Node market.
Microservices – State of Developer Ecosystem 2022 (JetBrains)
21–30 of 47 posts
Re: Microservices – State of Developer Ecosystem 2022 (JetBrains)
#22Earlier quoted context omitted.
Do we really want another religious war over microservices vs monoliths? Count me out. I'll adopt each for appropriate use cases.
> 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.
Re: Microservices – State of Developer Ecosystem 2022 (JetBrains)
#23Microservices 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…
> 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 in your situation, silly." I mean yeah, it is so simple and straightforward now why didn't everyone think of it before.
Re: Microservices – State of Developer Ecosystem 2022 (JetBrains)
#24I'm shocked Java is the most popular language. I thought it was primarily a Node market.
This is a survey conducted by JetBrains, whose primary product is a Java/Kotlin IDE. They do support other languages, but their audience is almost certainly skewed toward JVM users.
Re: Microservices – State of Developer Ecosystem 2022 (JetBrains)
#25Earlier quoted context omitted.
Do we really want another religious war over microservices vs monoliths? Count me out. I'll adopt each for appropriate use cases.
> 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.
Re: Microservices – State of Developer Ecosystem 2022 (JetBrains)
#26I'm shocked Java is the most popular language. I thought it was primarily a Node market.
You may be surprised, but in Europe, it's difficult to find a company that doesn't use Java (or .Net).
Node does exist, but it's not where the money is.
Re: Microservices – State of Developer Ecosystem 2022 (JetBrains)
#27So 63% of market still to be captured by microservices. I think it is great for boosting profit at cloud vendors, APM vendors, service mesh and so on. If I had made big tech level money, there is no better time to retire and move away from tech for me.
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
Re: Microservices – State of Developer Ecosystem 2022 (JetBrains)
#28Earlier 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?
> Silly me always thought Microservices was just a new word for SOA.
Lucky you. You were using “Microservices” the right way all the time, without even realising it.
Re: Microservices – State of Developer Ecosystem 2022 (JetBrains)
#29Microservices 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…
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.
Re: Microservices – State of Developer Ecosystem 2022 (JetBrains)
#30Earlier 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 think the failure of most group processes is the leadership's failings. They need the wisdom and technical knowledge to make the right choices, the organizational skill to implement those choices, the authority to implement those choices, and the charisma to bring the team along with them.
I know a lot of people get mad and lash out at Agile in particular, but I don't think the alternative is any more straightforward. Group work is hard.