Funqy HTTP Binding with Amazon Lambda
If you want to allow HTTP clients to invoke on your Funqy functions on AWS Lambda, Quarkus allows you to expose multiple Funqy functions through HTTP deployed as one AWS Lambda. This approach does add overhead over the regular Funqy AWS Lambda integration and also requires you to use AWS API Gateway.
This technology is considered preview.
In preview, backward compatibility and presence in the ecosystem is not guaranteed. Specific improvements might require to change configuration or APIs and plans to become stable are under way. Feedback is welcome on our mailing list or as issues in our GitHub issue tracker.
For a full list of possible extension statuses, check our FAQ entry.
Follow the Amazon Lambda Http Guide. It walks through using a variety of HTTP frameworks on Amazon Lambda, including Funqy.
|The Funqy HTTP + AWS Lambda binding is not a replacement for REST over HTTP. Because Funqy needs to be portable across a lot of different protocols and function providers its HTTP binding is very minimalistic and you will lose REST features like linking and the ability to leverage HTTP features like cache-control and conditional GETs. You may want to consider using Quarkus’s JAX-RS, Spring MVC, or Vert.x Web Reactive Route support instead. They also work with Quarkus and AWS Lambda.|
Beyond generating an AWS project that is covered in the Amazon Lambda Http Guide, there’s also a quickstart for running Funqy HTTP on AWS Lambda.
Clone the Git repository:
git clone https://github.com/quarkusio/quarkus-quickstarts.git, or download an archive.
The solution is located in the
There is nothing special about the code and more importantly nothing AWS specific. Funqy functions can be deployed to many different environments and AWS Lambda is one of them. The Java code is actually the same exact code as the funqy-http-quickstart.
The steps to get this quickstart running are exactly the same as defined in the Amazon Lambda HTTP Guide. This differences are that you are running from a quickstart and the maven dependencies are slightly different.
<dependency> <groupId>io.quarkus</groupId> <artifactId>quarkus-funqy-http</artifactId> </dependency> <dependency> <groupId>io.quarkus</groupId> <artifactId>quarkus-amazon-lambda-http</artifactId> </dependency>