AWS Lambda Runtime Interface Client

[Mark Sailes]

Hi everyone, I'm new to this community. I work at AWS as a specialist solutions architect for serverless. I work a lot with Lambda and help customers using Java. I'm also part of the team which supports our core open-source Lambda libraries.

Last year AWS open-sourced the runtime interface client used in the Java managed runtimes. This is a highly optimised client (https://github.com/aws/aws-lambda-java-libs/tree/master/aws-lambda-java-runtime-interface-client)

Would Quarkus consider moving to use this client instead of using its own? 

Advantages which I can see are.

• Less code for you to maintain
• Support for more event sources
• Serialization edge cases of events handled
• Lower latency for customers (the RIC uses cURL for network calls)

Thanks,

Mark

[Max Rydahl Andersen]

related issue https://github.com/quarkusio/quarkus/issues/16869

[Max Rydahl Andersen]

i am not an expert on this area but what would this entail ? that we default to use a different base image in the container or just using a different java client ? 

A PR would probably go a long way :)

[William Burke]

We don't have our own AWS client so there's nothing stopping our users from using AWS's.

--
You received this message because you are subscribed to the Google Groups "Quarkus Development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quarkus-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/quarkus-dev/8fcbb70a-14da-4030-8b07-eb7fc0315874n%40googlegroups.com.

--

Bill Burke

Red Hat

[William Burke]

Didn't realize Mark and I had been communicating privately.  I took a look at the runtime code he linked to.  It doesn't support overriding handler instantiation which we would need to support injection into handler instances.  We also might want to use our own serialization (i.e. QSON).  There's definitely a lot of code that has potential reuse.  In the least, its great to be able to *SEE* how things really work.  I'm going to take a look at this very soon and incorporate what we can.

@Mark Sailes  How open to PRs is AWS?  Would love to be able to add ability to control handler instantiation.

On Fri, Apr 30, 2021 at 7:59 AM Max Rydahl Andersen <mand...@redhat.com> wrote:

--
You received this message because you are subscribed to the Google Groups "Quarkus Development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quarkus-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/quarkus-dev/8fcbb70a-14da-4030-8b07-eb7fc0315874n%40googlegroups.com.

[William Burke]

Our current integration is for java and custom runtime deployment.  Our poller only comes into play for the custom runtime deployment (graal native build).  Never really looked into the container approach as it's a few extra steps.  AFAIK, nobody has really asked us for anything around container support and seem to be pretty happy with java or custom runtime.  What are the advantages of container approach considering the extra complexity it requires?

On Fri, Apr 30, 2021 at 12:37 PM Mark Sailes <ma...@sailes.co.uk> wrote:

I think it would probably be worth a chat before you started any work. The primary use case is container support for Lambda and visibility for that.

[Mark Sailes]

I think it would probably be worth a chat before you started any work. The primary use case is container support for Lambda and visibility for that.

On Fri, 30 Apr 2021, 17:24 William Burke, <bbu...@redhat.com> wrote: