But that is the thing.
It just means that instead of using the language features and creating clean interfaces across modules, they were witting spaghetti code.
With microservices they get to write spaghetti REST calls with the added fun of distributed computing failures.
Normal software libraries also have sharp boundaries with clear interfaces. Why use shitty RPC-over-HTTP? At the very least you can use something sane like Thrift.
Re:The End of Microservices
by sanmon3186 on Thursday July 21, 2016 @05:31AM
(#12135738)
> the replacability is usually much better due to being forced to define sharp boundaries with clear interfaces
If by "sharp boundaries with clear interfaces", you mean API specification, how is it a microservice thing? I thought the benefits of microservices lie in behind-the-scenes details.
However, the replacability is usually much better due to being forced to define sharp boundaries with clear interfaces.