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

Support Async APIs for Lambda RequestHandler Interface #1164

Open
bytekast opened this issue May 18, 2017 · 9 comments
Open

Support Async APIs for Lambda RequestHandler Interface #1164

bytekast opened this issue May 18, 2017 · 9 comments
Assignees
Labels
feature-request A feature should be added or improved.

Comments

@bytekast
Copy link

bytekast commented May 18, 2017

perhaps something like

public interface RequestHandler<I, O> {
  public Future<O> handleRequest(I input, Context context);
}
@shorea shorea added the feature-request A feature should be added or improved. label May 19, 2017
@shorea shorea self-assigned this May 22, 2017
@shorea
Copy link
Contributor

shorea commented Jun 8, 2017

Apologies for the delay. This seems to be a feature request for the actual lambda handler, is that a correct assumption? I.E an addition to http://docs.aws.amazon.com/lambda/latest/dg/java-programming-model-handler-types.html

@bytekast
Copy link
Author

bytekast commented Jun 8, 2017 via email

@shorea
Copy link
Contributor

shorea commented Jun 8, 2017

Gotcha, we don't control the handler side of things. That's managed by the Lambda service team. I can pass this feedback along to them. Could you provide more details on your use case and why returning a future is desirable, I'm having trouble wrapping my head on how that will work with the lambda container architecture. Any details you can provide will help the service team with prioritization.

@bytekast
Copy link
Author

bytekast commented Jun 8, 2017

@shorea its essentially the same async callback mechanism provided in the JavaScript handler. Many JVM frameworks/applications now support async handlers. It would be nice if the AWS Lambda Java SDK supports this programming model as well.

@pendula95
Copy link

Is there any progress on this? Example: Vertx framework. If I want to implement custom API gateway that would be invoked from http request, I need a async http request handler for lambda as vertx is a async framework. As @shorea mention this is already supported in AWS JavaScript handler.

@dagnir
Copy link
Contributor

dagnir commented Oct 19, 2017

@pendula95 Have you opened a ticket through the AWS Support Center? It might be a more expedient approach since you'll have a more direct line of communication with Lambda that way.

@pendula95
Copy link

I am only testing features to see if AWS is suitable for our use case. I only have Basic Support Plan so I can't contact technical support.

@RichardSilveira
Copy link

+1 (additionally on it, it´s normal return a 202 response on REST API´s...)

@muhammadssr
Copy link

Nothing on this yet?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request A feature should be added or improved.
Projects
None yet
Development

No branches or pull requests

6 participants