spring - Is this the best architecture/design to handle requests with large payload and heavy time-consuming process to handle each request in Java Ecosystem? -


which best architecture handle multiple http requests sending list of ids (with more 1000 ids in each request) , each request heavy time-consuming process communicate other systems (that uses soap or rest) , saves data rdbms?

should send ids in post http request?

should use spring framework async/futures (without return) in resource/controller rest handle time-consuming process , return http 202 accepted (and maybe id query status of process or resource)?

or if resources/controllers rest put messages in jms queue (maybe persistent queue each rest method) , message-driven beans (for each method) consume messages , process request?

it idea if resources/controllers rest or class acting proxy save requests system , other systems responses in database logging purposes , fix problems? or should use retry feature in jms example?

i agree dunni; however, general requirements sound jms place start. allow clients drop off requests , allow end components work on requests able. of course, need enough end power requests completed in reasonable time frame.


Comments

Popular posts from this blog

node.js - Node js - Trying to send POST request, but it is not loading javascript content -

javascript - Replicate keyboard event with html button -

javascript - Web audio api 5.1 surround example not working in firefox -