amartinsn

4 ms·

1. 1.▲
   by amartinsn 10y ago

   Our scenario looked a bit similar to yours mate!
2. 2.▲
   by amartinsn 10y ago

   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
3. 3.▲
   by amartinsn 10y ago

   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.
4. 4.▲
   by amartinsn 10y ago

   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
5. 5.▲
   Lessons Learned from Software Rewrites(alexmartins.me)

   196 points by amartinsn 10y ago|84 comments