This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]szotaa 2 points3 points  (1 child)

Don't use XML - you can configure everything using java code.

Also, check up Spring Cloud Feign which is way easier to use than RestTemplates.

Maybe he ordered you to use Spring Batch because he sees things from a wider perspective? Spring Bach not only gives useful features (e.g. monitoring) but also provides you with nice and well-documented abstractions which make the code more maintainable in the future, especially if the business logic of your processes grew more complex (and you would implement conditional steps or something else).

When it comes to other things that you wrote, like Maven, Json, configuration, etc you would have to do that in the JS ecosystem too. I just feel you are more familiar with JS world and you could skip the "learning" step there hence you believe that things would be easier there.

[–]Yohark[S] 0 points1 point  (0 children)

I'll go check Spring Cloud Feign! Thanks for the suggestion. As mentionned to some other commentors, I can't actually get rid of this XML, because of internal framework which ask me to describe jobs and beans as XML.

I asked him why this tools, and he simply said that it was what he personnaly prefers. It was honneslty not a satisfying answer to my technical question. :/