Messaging between frontend and stateful backend throughout computation
up vote
-1
down vote
favorite
I am designing an backend system that receives data from the frontend (user input) via API calls. The computation occurs in a loop until conditions are met. Each iteration of this loop requires additional user input, which is supplied by API calls to a particular route.
Currently, we have a Flask server as the API endpoint which begins the computation loop in a separate thread. Subsequent API calls to another endpoint supply the thread with the user input. We now have the problem of transmitting the "completed" status back to the front end. Note: I am trying to get this working for a single user before scaling the solution.
We thought that using sockets could help solve this issue (when the socket closes the connection, the computation is done, but no data is transmitted via the socket), but it seems like a complicated solution to a seemingly simple problem.
Someone mentioned that the use of RabbitMQ or even moving our implementation to Go to use Goroutines and Go Streams could solve this problem. Are these appropriate solutions to the problem I am having?
Any thoughts on how we could architect this system efficiently and easily?
python flask backend api-design
asked Nov 19 at 21:42
Jad Chaar
14
add a comment |
up vote
-1
down vote
favorite
I am designing an backend system that receives data from the frontend (user input) via API calls. The computation occurs in a loop until conditions are met. Each iteration of this loop requires additional user input, which is supplied by API calls to a particular route.
Currently, we have a Flask server as the API endpoint which begins the computation loop in a separate thread. Subsequent API calls to another endpoint supply the thread with the user input. We now have the problem of transmitting the "completed" status back to the front end. Note: I am trying to get this working for a single user before scaling the solution.
We thought that using sockets could help solve this issue (when the socket closes the connection, the computation is done, but no data is transmitted via the socket), but it seems like a complicated solution to a seemingly simple problem.
Someone mentioned that the use of RabbitMQ or even moving our implementation to Go to use Goroutines and Go Streams could solve this problem. Are these appropriate solutions to the problem I am having?
Any thoughts on how we could architect this system efficiently and easily?
python flask backend api-design
asked Nov 19 at 21:42
Jad Chaar
14
add a comment |
up vote
-1
down vote
favorite
up vote
-1
down vote
favorite
I am designing an backend system that receives data from the frontend (user input) via API calls. The computation occurs in a loop until conditions are met. Each iteration of this loop requires additional user input, which is supplied by API calls to a particular route.
Currently, we have a Flask server as the API endpoint which begins the computation loop in a separate thread. Subsequent API calls to another endpoint supply the thread with the user input. We now have the problem of transmitting the "completed" status back to the front end. Note: I am trying to get this working for a single user before scaling the solution.
We thought that using sockets could help solve this issue (when the socket closes the connection, the computation is done, but no data is transmitted via the socket), but it seems like a complicated solution to a seemingly simple problem.
Someone mentioned that the use of RabbitMQ or even moving our implementation to Go to use Goroutines and Go Streams could solve this problem. Are these appropriate solutions to the problem I am having?
Any thoughts on how we could architect this system efficiently and easily?
python flask backend api-design
asked Nov 19 at 21:42
Jad Chaar
14
I am designing an backend system that receives data from the frontend (user input) via API calls. The computation occurs in a loop until conditions are met. Each iteration of this loop requires additional user input, which is supplied by API calls to a particular route.
Currently, we have a Flask server as the API endpoint which begins the computation loop in a separate thread. Subsequent API calls to another endpoint supply the thread with the user input. We now have the problem of transmitting the "completed" status back to the front end. Note: I am trying to get this working for a single user before scaling the solution.
We thought that using sockets could help solve this issue (when the socket closes the connection, the computation is done, but no data is transmitted via the socket), but it seems like a complicated solution to a seemingly simple problem.
Someone mentioned that the use of RabbitMQ or even moving our implementation to Go to use Goroutines and Go Streams could solve this problem. Are these appropriate solutions to the problem I am having?
Any thoughts on how we could architect this system efficiently and easily?
python flask backend api-design
python flask backend api-design
asked Nov 19 at 21:42
Jad Chaar
14
asked Nov 19 at 21:42
Jad Chaar
14
asked Nov 19 at 21:42
Jad Chaar
14
asked Nov 19 at 21:42
Jad Chaar
14
asked Nov 19 at 21:42
Jad Chaar
14
14
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53383058%2fmessaging-between-frontend-and-stateful-backend-throughout-computation%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
