Working on migration of old application written in groovy-grails along with spring-integration framework.
Application has different APIs written and Spring-Integration is mainly here to drive flow of API logic to call sequence of actions and retry logic.
Now our planning to to migrate this application to Spring-Boot. So I am seeking expert advices/opinion here from application design point of view as explain below.
Current business logic can explain shortly as below
def API1(inputMessageObject){
try{
callstep1(inputMessageObject)//{..if not already completed}
callstep2(inputMessageObject)//{..if not already completed}
callstep3(inputMessageObject)//{..if not already completed}
....
}catch(Exception e){
inputMessageObject.setErrors()
}
Based on above code logic requesting answers on following questions
1.Should keep using Spring Integration in new design? Advantage is- less if else in code in terms of calling sequence of steps but another thought could be, is Spring integration is right candidate here to use and make it little complex.
2.If we are not going with Spring Integration then need another good way to manage retry logic here.
As per current retry logic drive by Spring Integration is, it checks non empty errors in input message body and redirects to Error Channel where depending on values /input data from message object it decides whether to retry or not , if yes then it sets new values in message object and sets channel dynamically where to start again.
I was checking Spring boot retrytemplate way, but there as well i feel cant set dynamic retry count or resetting inputs while retrying
Please suggests, any opinions are appreciated. Thanks.
