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
Hi,
I tried several experiments to get a simple Micronaut application with an endpoint running which delivers a couple of strings, where each string is delayed by 1sec (implemented as Publisher<Event<String>>). Locally, it was possible with the netty dependency in place. Deployed as GraalVM lambda with a gateway the response was buffered and all strings were returned at once. After some research I discovered that this buffering is the intended behavior of the gateway.
Further research brought me to the announcement that AWS Lambda Function URL supports response streaming: https://aws.amazon.com/blogs/compute/introducing-aws-lambda-response-streaming/
Response streaming should work in combination with a custom runtime. So in theory there should be no problem to get SSE running. Unfortunately I did not find a solution. I even tried an own implementation of AbstractMicronautLambdaRuntime and RequestStreamHandler because the function URL uses gateway V2 events. So is there any deeper documentation regarding this problem or even better a working solution?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I tried several experiments to get a simple Micronaut application with an endpoint running which delivers a couple of strings, where each string is delayed by 1sec (implemented as
Publisher<Event<String>>
). Locally, it was possible with the netty dependency in place. Deployed as GraalVM lambda with a gateway the response was buffered and all strings were returned at once. After some research I discovered that this buffering is the intended behavior of the gateway.Further research brought me to the announcement that AWS Lambda Function URL supports response streaming: https://aws.amazon.com/blogs/compute/introducing-aws-lambda-response-streaming/
Response streaming should work in combination with a custom runtime. So in theory there should be no problem to get SSE running. Unfortunately I did not find a solution. I even tried an own implementation of
AbstractMicronautLambdaRuntime
andRequestStreamHandler
because the function URL uses gateway V2 events. So is there any deeper documentation regarding this problem or even better a working solution?Best regards and thanks!
Beta Was this translation helpful? Give feedback.
All reactions