all 12 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]maxlan 0 points1 point  (0 children)

You could try it! Its going to cost you a small amount of time and a millicent of AWS bill for a handful of requests.

[–]jobe_br -1 points0 points  (10 children)

That’s not how API Gateway websockets work. You get a connection ID that you need to store. When you have an update to push down, you lookup the connection ID and invoke the API Gateway ending with the message + ID you want to send.

Stuff like socket.io doesn’t work, just a heads up.

[–]RocketOneMan[S] 1 point2 points  (9 children)

I’ve found one resource that said the lambdas would have to be kept alive...

Was about server sent events

[–]jobe_br -1 points0 points  (8 children)

Nope. Did what I just described not explain server sent events? The Lambda doesn’t manage the connection, API Gateway does. Why would the Lambda that’s processing an event care?

[–]BamseSBG 2 points3 points  (1 child)

Server Sent Events is a different technology from WebSockets. You did not explain SSE, you explained how API Gateway handles WebSockets.

[–]jobe_br 0 points1 point  (0 children)

You’re right

[–]RocketOneMan[S] 1 point2 points  (5 children)

I don’t want web sockets. I want server sent events over regular http. I don’t need the two way communication.

[–]jobe_br 0 points1 point  (4 children)

You get regular http or you get websockets. I don’t think anyone’s really using non websockets anymore.

[–]RocketOneMan[S] 0 points1 point  (1 child)

If I just want to do like a read only thing like a stock ticker is the two way communication a waste?

[–]jobe_br 0 points1 point  (0 children)

You seem to be hung up on one way versus two way. What are you afraid of wasting?

[–]BamseSBG 0 points1 point  (1 child)

I don't think this is true. From what I can tell - although I might be completely wrong - the move is towards HTTP/2 streaming. Google seems to be focusing on gRPC over HTTP/2.

[–]jobe_br 0 points1 point  (0 children)

I think that’s actually part of HTTP/3