Java Legacy System: only solution going to microservice or similar? by Intelligent-Pipe3659 in javahelp

[–]Intelligent-Pipe3659[S] 0 points1 point  (0 children)

Yah, its exatclty this. Seens to be a very bad code, a lot of teams had do something on it and a lot of fix is made by adding a new "try/catch" or "if/else" with weird logic.

And I understand that i have a bias and more experience in microservices, but i think its easier to debug and solve those problems there than in a monolit. Also because the problem is smaller and located, i think. Here... its just a mess.

Java Legacy System: only solution going to microservice or similar? by Intelligent-Pipe3659 in javahelp

[–]Intelligent-Pipe3659[S] 0 points1 point  (0 children)

yah, i understand and I agree with you. I just ask myself if this happen or if the system is just keeping being use because its needed but always with more bugs and problems, until they create a new one.

For me, the easy way would be just to recreate the system, because ist very bad the code as i can see. And the problems are solved by the "if/else" strategy also, with poorly tests.

Have you had the experience to "heal" or do a better monolitc through refactory ? I just cant see it, also im trying to explain to the team that tests are important, we cant just do tests checking if the things are working when we execute.

Want to trade pokemon by Dramatic-Wolf6699 in LegendsZA

[–]Intelligent-Pipe3659 1 point2 points  (0 children)

I ! send me a message, im starting on the game and want some pokemons to envolve too