Live data from Hacker News

The End of Microservices

lightstep.com

151–154 of 154 posts

Re: The End of Microservices

#151
post #150
post #148

Earlier quoted context omitted.

> I described some of the benefits I am currently experiencing from using microservices where we previously had a monolith. Sure - I do appreciate it. It's just that my experience in a company that used both was that the microservices weren't worth it - more generally I think a lot of people leap on microservices without thinking about other ways to achieve what they want - so I want to fully work through the options…

> I've actually come to think that the best languages are general-purpose languages and you should just use one language (Scala) for everything. I disagree very strongly with this. My original background is in scientific programming, which I learned primarily during my PhD. Since then I've been working in, and now leading, teams comprised of both data scientists (principally from a scientific or mathematics backgroun…

Shrug. In a previous job I ported scientific code from R to Scala and 99% of the time it was very straightforward. I'm not saying that scientific code is easier than any other code (if anything the opposite is true), I'm saying that the things that make a good language for science are the same things that make a good language for anything else.

Re: The End of Microservices

#152

nitpick: nice graph on the "information superhighway" but a label about exactly what is being measured (0.000055%, of what ) would be great. Is this a word count? Or its rate of change? There's a reason our (stuffy) professors/sub-editors always insist on sources and accurate labeling. I'm only interested because the most recent data points, despite large decline, still suggest a non-negligible use of a term which I…

It's just % of bigrams that appear in Google's sample of books. [1] Not especially meaningful, I admit!

[1] https://books.google.com/ngrams/info

Re: The End of Microservices

#153
post #129

"Microservices" are a new name for a very old concept. This is just low-coupling, high-cohesion by another name. Small, composable, decoupled, highly cohesive components are what "good" software has been about for decades, but it now has a new name in the server s/w world; "Microservices". Only the name is new & hyped. The concepts have been true forever.

There is software and concepts around managing microservices that didn't exist before, and so on. Nothing can be new when you use such a vague way of comparing things. There were electric cars in the 1800s, why talk about Tesla?

...so what is a new concept regarding microservices?

I don't see anything new... new tools, granted. Then again, there's new tools being produced every day for every architectural style.

Re: The End of Microservices

#154
post #54

Earlier quoted context omitted.

It's especially fun when you get to write the monolith 3 times over for web, ios and android.

Why would you write it three times? You write it once, have it expose an API. Have your Web, IOS and Adroid client use the said API. Easy pease. Optional: allow your customers to use the API, too.

That's not 'microservices'
Post reply on HN