3 ms·
Won't the fact you need to only replace some parts with well-defined interfaces help? In my company, we had a legacy PHP system that seemed to me excessively
by nine_k 9y ago
Won't the fact you need to only replace some parts with well-defined interfaces help?
In my company, we had a legacy PHP system that seemed to me excessively layered and cut too thinly. In reality, it allowed to completely replace that system with Python and Java piecemeal, without ever stopping it.
- maxxxxx 9y agoNow imagine in 10 years someone comes in and has to figure out how all these services written with outdated libraries fit together and how to fix bugs.
- nine_k 9y agoHTTP does not get outdated for quite some time already. The standard connection points with extremely late binding is what makes microservices somehow easier to update, as opposed to rebuilding a monolith. Fitting together is an aspect that becomes easier when you decompose your app properly microservices or not. When a component has clear responsibilities, it's easy(-ier) to understand, modify, and replace. When a component is reasonably small and isolated, it's easy(-ier) to analyze and understand, even if it's written in an ancient language using dust-covered unmaintained libraries.