I have a problem with the business logic of a specific process of a Java web service based on the Spring Boot framework, and I am wondering if I can use AWS lambda to solve it. Even if it is not an AWS lambda function, if it is possible to solve it in another way, please advise.
The business logic of the process in question is as follows.
- A specific member logged in to his/her own page (total of 3 sites that can log in)
- Expose an alert window above the member information modification guide pop-up window (related to member code misregistration at the time of registration)
- Update member code using API when clicking the OK button (reflecting A RDS)
- Based on the changed member code, #2 pop-up screen reconfiguration (the code is also used for other screen configurations)
- After entering the remaining member information on the reconfigured screen, save member information using API (reflecting A RDS)
The problem here is the situation where the process hangs at #3. It is possible to shut down the computer or browser on the client. After that, if the member logs in to the other two sites, there is a problem with the screen configuration because the data for #5 is not saved. The other two sites are looking at the member code, and exception handling is not possible. Is there any way to roll back the member code again if the process is interrupted from step #3? Is there a way to solve the problem by adding functions without modifying the process up to #5?