3 ms·
I realize this is a naive perspective, but rather than try to “translate millions of lines of COBOL to Java”, why not just build a new system from the ground up
by rzz3 6y ago
I realize this is a naive perspective, but rather than try to “translate millions of lines of COBOL to Java”, why not just build a new system from the ground up, based on requirements and first principals? The function of these systems seems fairly simple from the outside. What am I missing?
- Guthur 6y agoAs someone else pointed out, there are no requirements the code is the only source. A long time ago I work on the core processing system for a large US insurer, the business would continually call up for confirmation on the business rules from the code. Not a basis for success on complex business laden with tonnes of regulatory oversight.
- rzz3 6y agoAbsolutely, but for systems like this, there should be clean separation between business rules and core application logic. Filters, hooks, rules engines, etc. I very much realize “easier said than done” but the complacency with regard to keeping these systems the way they are is truly alarming.
- commandlinefan 6y agoThat would take a long time and can’t be realistically predicted (even if it could, the prediction would be months). Management will never ok a development effort whose schedule isn’t predicted as more than a few weeks (ESPECIALLY in fin tech).
- bingojess 6y agoFor companies like banks, the transition is the riskiest part. For management, there is no upside in such projects since the system already works, but downsides are project failure and your banking systems ceasing to work. Not to mention cost.
- stjohnswarts 6y agothe only thing driving change on such a system is when it can no longer to scale to handle the "traffic" or legislation that forces it.