Re:An Apology to COBOL: Maybe Old Technology Isn’t the Real ...
by nnamtr on Wednesday April 07, 2021 @05:04AM
(#26722095)
$reason = Make the microservices independent of each other, so you can rewrite and replace them without much trouble when they're getting old.
[ Parent
| on HN ]
Re:An Apology to COBOL: Maybe Old Technology Isn’t the Real ...
by tovej on Wednesday April 07, 2021 @05:43AM
(#26722459)
This is just modularisation though. You can modularise without microservices. Microservices solve a scaling problem, not a design flexibility problem.
Re:An Apology to COBOL: Maybe Old Technology Isn’t the Real ...
by iampims on Wednesday April 07, 2021 @06:05AM
(#26722647)
Micro services often solve _an organizational scaling_ problem, and are less frequently deployed for _performance scaling_.
Re:An Apology to COBOL: Maybe Old Technology Isn’t the Real ...
by beaconstudios on Wednesday April 07, 2021 @06:57AM
(#26723071)
a monorepo also solves that same organisational scaling problem, but without introducing the artificial problem of basic function calls having to traverse the network, and having to keep tons of different services online and talking to each other.
Re:An Apology to COBOL: Maybe Old Technology Isn’t the Real ...
by fennecfoxen on Wednesday April 07, 2021 @07:29AM
(#26723309)
Yeah, but it turns out people can’t actually write software right (or won’t) and this sort of network boundary is the only way to force them to write modular code, without the monolith collapsing into a tangled mess.
It’s really annoying.
Re:An Apology to COBOL: Maybe Old Technology Isn’t the Real ...
by beaconstudios on Wednesday April 07, 2021 @07:32AM
(#26723328)
yes one of the biggest problems in software development is that most developers are bad at their jobs.
the solution, however, would be to hire a small number of really good developers and have code reviews run through them - hopefully teaching the more average developers how to code better in the process.
Re:An Apology to COBOL: Maybe Old Technology Isn’t the Real ...
by emodendroket on Wednesday April 07, 2021 @07:41AM
(#26723384)
It’s so simple. You just need to devise the world’s first 100% predictive interview process
Re:An Apology to COBOL: Maybe Old Technology Isn’t the Real ...
by beaconstudios on Wednesday April 07, 2021 @09:00AM
(#26724232)
I wish it were easy. The most important things to do are usually pretty hard, or they'd be done already.
Re:An Apology to COBOL: Maybe Old Technology Isn’t the Real ...
by ABeeSea on Wednesday April 07, 2021 @07:08AM
(#26723161)
Since servers are ephemeral, any function call of note will need to traverse the network in some way anyway.
Re:An Apology to COBOL: Maybe Old Technology Isn’t the Real ...
by beaconstudios on Wednesday April 07, 2021 @07:22AM
(#26723246)
that's true, but there's traversing 2 links for a simple client<->server<->database setup, or traversing dozens or even hundreds of links for a microservice architecture, adding tons of fragility for no unique benefit.
Re:An Apology to COBOL: Maybe Old Technology Isn’t the Real ...
by asimpletune on Wednesday April 07, 2021 @05:58PM
(#26731928)
Well, there are legitimate benefits, it's just that few organizations are poised to understand/utilize them.
Re:An Apology to COBOL: Maybe Old Technology Isn’t the Real ...
by toomanybeersies on Wednesday April 07, 2021 @10:52AM
(#26725785)
The flip side to that is that you end up with a dozen services built with different technologies/languages and you spend all your time upgrading them or replacing them instead of building new features.
At least one of them will be guaranteed to be built with some technology/language (probably Scala or Elixir) that one of your engineers (who's since left) was interested in for a few weeks.