Re:Goodbye Microservices: From 100s of problem children to 1...
by ljw1001 on Tuesday July 10, 2018 @05:12PM
(#17502224)
like all those simple airline reservation and banking systems?
[ Parent
| on HN ]
Re:Goodbye Microservices: From 100s of problem children to 1...
by wsy on Tuesday July 10, 2018 @05:37PM
(#17502414)
Yes, they do fine as examples. I have worked both on decades old booking systems and banking software. Both were dependency hells. Refactoring was impossible. Everybody was super-careful even with tiny changes because the risk to break something was just too high.
If it could be avoided, these systems were not touched anymore. Instead, other applications where attached to the front and sides.
Re:Goodbye Microservices: From 100s of problem children to 1...
by collyw on Wednesday July 11, 2018 @03:27AM
(#17505071)
Isn't that a feature of old systems in general?
Re:Goodbye Microservices: From 100s of problem children to 1...
by wsy on Wednesday July 11, 2018 @08:34AM
(#17506340)
I don't think so. For example, the Linux kernel is old, but still quite well maintainable.
So I would say: it applies to systems where proper modularization was neglected. In the anecdotical cases I referred to, one major element of this deficiency was a complex database, shared across the whole system.