3 ms·
the discussion about the difficulty of testing microservices makes me wonder how the programmers in 20 years will look at the currently modern systems that are
by maxxxxx 9y ago
the discussion about the difficulty of testing microservices makes me wonder how the programmers in 20 years will look at the currently modern systems that are being built now. Let's say the system has been in use for 10 years, everybody has moved on and now you have to make extensions or bug fixes to a legacy cloud/microservice/multi-language/multi-server/distributed/queuing/ system. At first look this makes updating an old COBOL system where you have one big codebase in one place look easy in comparison.
- DenisM 9y agoI call it the circle of life. Old code devoid of support, and with it old systems and old companies even, wither and die to make way for new code, new systems, and new companies. Sometimes the new thing is the same as the old thing, sometimes it’s really new.
- nine_k 9y agoWon'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.