amartinsn
Re:Lessons Learned from Software Rewrites
on Tuesday September 06, 2016 @02:14PM (#12438020)
Our scenario looked a bit similar to yours mate!
Re:Lessons Learned from Software Rewrites
on Tuesday September 06, 2016 @02:12PM (#12438004)
That was exactly our approach, for the old HTTP API, we kept the same contracts (URIs, response body, etc.) For the EJB one, as only one remaining client was using it, we deprioritized that, but we were going to pick the features they were using, and make the Java client point to the new API implementation, also keeping the same contract.
Re:Lessons Learned from Software Rewrites
on Tuesday September 06, 2016 @02:05PM (#12437962)
It's an incremental rewrite. Rewrite one feature, switch everyone to use it, then destroy the old implementation. Do the same for all other features.
Re:Lessons Learned from Software Rewrites
on Monday September 05, 2016 @07:50AM (#12429622)
Hey, thanks for your reply. Your line of thought is very similar to what we had. We considered refactoring the existing Java implementation. It used a really old Jersey version, with too many overengineered customizations tightened to that version. We tried to upgrade it and get rid of some of those customizations, but the system was so fragile that other parts of the system stopped working, which made that a really difficult road to drive. We wanted to simplify the design. We chose Scala and Finagle for the new stack.