Re:Goodbye Microservices: From 100s of problem children to 1...
by badasstronaut on Tuesday July 10, 2018 @01:13PM
(#17500111)
Personally, I don’t like the terms ‘microservices’ or ‘nanoservices.’ What’s the value add in describing the relative size of the service? The _domain_ should drive what becomes its own service. Every service should handle the business logic within a particular domain. It’s definitely a goldilocks problem, though, in that there’s a too-small and too-large, and we’re looking for the just-right fit!
[ Parent
| on HN ]
Re:Goodbye Microservices: From 100s of problem children to 1...
by jacquesm on Tuesday July 10, 2018 @01:33PM
(#17500335)
That's exactly it. But when you start doing 'microservices' you get the architecture astronauts who go and see into how many silly little services a monolith can be broken up. The end results are as predictable as the original monolith, both end up as an unmaintainable mess in a couple of years.
I predict the same will happen to the 'superstar', it just isn't old enough yet (and at least it was built with some badly needed domain knowledge).