3 ms·
Replacing a single legacy system with another system that does exactly the same thing is expensive, risky, and wins you almost nothing. You have to replace a la
by stcredzero 10y ago
Replacing a single legacy system with another system that does exactly the same thing is expensive, risky, and wins you almost nothing. You have to replace a large chunk of the whole legacy all at once, without disrupting your day to day business. This is hard to do; any project to try this is likely to fail before it really gets started.
The way to do this is to create an automatic translation tool. Furthermore, this translation tool can't be generic. Instead, it has to map the idioms of the legacy project to new code in the idioms of the new environment. Done properly, doing the port at one level of indirection like this, you can absorb all of the changes to the legacy system as they are happening, then instantly switch over when the new system is finally ready.
- PaulAJ 10y agoGot any case studies where that worked?
- stcredzero 10y agoThere was a consulting shop that did nothing but this for Smalltalk to Java. I also did such a project. Yes, this works, given good parser tools with scripting and full syntactic expressiveness.