Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Problem: polling is not a perfect solution. Find another solution. #9

Open
allensuvorov opened this issue Apr 27, 2023 · 0 comments
Open

Problem: polling is not a perfect solution. Find another solution. #9

allensuvorov opened this issue Apr 27, 2023 · 0 comments

Comments

@allensuvorov
Copy link
Owner

allensuvorov commented Apr 27, 2023 •
edited
Loading

"Implemented task polling with timeout. With this approach, we can go to the database without receiving new data, or vice versa, forcing the user to wait an extra 500ms until it's time to go for tasks. At this point, we expected to see work with channels, when, after writing to the database, the request handler is immediately launched."

Which would it be, to keep services decoupled?

  • message queque
  • gRPC
  • other?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@allensuvorov