You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: