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.

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

Indirect output communication #15

Open
3 of 5 tasks
mcopik opened this issue May 27, 2022 · 1 comment
Open
3 of 5 tasks

Indirect output communication #15

mcopik opened this issue May 27, 2022 · 1 comment
Labels
enhancement New feature or request priority

Comments

@mcopik
Copy link
Collaborator

mcopik commented May 27, 2022

Our current communication between FK functions and clients relies on clients being able to listen on a TCP socket. Unfortunately, this requires clients to have a public IP and not behind a NAT.

An alternative solution would be to use a cloud queue. Clients perform long polling to read messages from writer, watch and heartbeat function.

  • Allocate new SQS queue.
  • Change distributor and watch functions to send notifications using the queue.
  • Change heartbeat function to use the queue to send messages and receive a reply.
  • Allocate dynamically SQS queues for new clients.
  • Modify client libraries to read messages intended only for this client instead of reading TCP socket.
@mcopik mcopik added the enhancement New feature or request label May 27, 2022
@mcopik mcopik added the good first issue Good for newcomers label Feb 16, 2023
@ziadhany
Copy link
Contributor

ziadhany commented Apr 8, 2023

@mcopik I think we have clientQueue . Do we need to create a new SQS queue ?

@mcopik mcopik removed the good first issue Good for newcomers label Mar 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request priority
Projects
None yet
Development

No branches or pull requests

2 participants