2 Answers
Hi J,
I was leaving this question alone as I personally don’t have any advise, but maybe that other forum members had some experience in this area. Doesn’t seem like it though.
In general, I’m not a fan of the "please stand by" type of feedback loops for web-based apps. Leaves too much possibility for loosing the connection of something strange happening in that process like a delay for warm-up in the Lambda function. For example, with LinkedIn, if you upload a video, they perform some transcribing I guess and notify you via push notification to the mobile app that your video post is ready.
That said, there are all sorts of new things coming out with the proliferation of PWAs. Sorry for the non-answer.
–Scott
There’s a good re:Invent session that describes some async / callback patterns and pro’s and con’s. Definitely have a look to reinforce your ideas and see what alternatives are possible. The patterns more towards the end, but it’s a good video entirely: https://youtu.be/dzU_WjobaRA?t=2399
One of the options also includes doing the async REST request and then opening a WebSocket in which the backend can reply back on when its done. (the example uses StepFunctions to check if both the connection is opened based on the unique client ID and the backend processing is done).