Dual Spring Boot and AWS Lambda Project



Sometimes, we need to convert an existing Spring Boot application to AWS Lambda function, often due to upgrade in technology or company's new direction to the sky.. I mean cloud and beyond...

In some extremely rare case we might be forced to write a dual Spring Boot and AWS Lambda project, that is a project that can run as a Spring Boot application in its embedded Tomcat container and also can be uploaded as AWS Lambda function. This usually happens when one of the developer in the team has had one too many "discussions" about Spring Boot or Lambda that he proceeded to create dual app while the rest of the team going round and round in circle.

Luckily, awslabs has answer to that, they call it Serverless Java Container:  https://github.com/awslabs/aws-serverless-java-container


Here is my simple example on how to achieve the dual Spring Boot x AWS Lambda application:

The source: https://github.com/overtakerx/springbootawslambdademo contains a simple typical Spring Boot application with four additional items:


aws-serverless-java-container-spring library as dependency in build.gradle

a task to build a zip file besides the original spring boot jar

new StreamLambdaHandler class


Spring Boot main application has to extend SpringBootServletInitializer



You could try ./gradlew bootRun and you can see that the Spring Boot application still functions as it should be, because it simply ignore the Handler class.

The AWS Lambda part is slightly trickier, go to AWS Lambda console and upload the zip file that has been assembled (note do not upload the spring boot jar file, it would not work)

Next, do not bother to get the test to work in AWS Lambda console, it requires you to recreate the massive aws proxy request json, which in my opinion, is too much of a work. Instead, go to API Gateway console...



And create a new API endpoint or reuse any of your existing one, and create a new child resource and configure it as proxy resource (this is important, if you don't do this one, you will be scratching your head for hours), leave everything as is and click create.




Finally, on the API Gateway test page, we specify the Method, the Path, Request Body if needed and Header (note this is important too as our Spring Boot application is expecting json, it needs to have the right content type header or else it will just return internal server error).

That's it!, of course this is grossly over simplified demo of the dual app, however it is a good beginner start, and a proof that it is do-able, happy dualing!


Further Reading:




Comments

Post a Comment

Popular posts from this blog

Image
Implementing gRPC Using Spring Boot and Gradle Background GRPC (gRPC) is a RPC framework pioneered by google later on made public and open source. GRPC has not been officially supported by Spring Framework, so far there are few community libraries that can work seamlessly with Spring Boot. In this article, I will use the lognet's grpc-spring-boot-starter. Project Structure Ideally, the proto files for gRPC is located in another directory, which will then be accessed by the gradle plugin to auto generate the required files.   Gradle Script The heart of gRPC enablement lies on the grpc boot starter, which includes few other tasks outlined as below. https://github.com/overtakerx/grpcbootdemo/blob/main/build.gradle Few important note: first you have to run gradlew compileJava for the auto generation to generate the files from the proto file, then you will need to rebuild the project for Intellij to recognise the auto-generated files. Full demo: https://github.com/overtakerx/grpcbootdem
Read more

Spring Boot 2: Parallelism with Spring WebFlux

Image
Spring Boot 2: Parallelism with Spring WebFlux Parallelism is rather unusual in Spring application, however when we encounter the need of HITLOL (HIgh Throughput LOw Latency), we need ways to make async calls. With Spring Boot 1, in high level definition, we can declare async on all the functions that are meant to be parallel and return Futures from there. Here is more detailed info:  https://medium.com/sipios/how-to-make-parallel-calls-in-java-springboot-application-and-how-to-test-them-dcc27318a0cf For Spring Boot 2, we shall employ Spring WebFlux libraries to accomplish parallelism. Mainly focused on functions: Mono.zipDelayError(), Mono.subscribeOn() and Mono.onErrorResume() The main function that drives the parallelism is zipDelayError(), the purpose of zipDelayError() as supposed to using zip() is to enable the other Monos to run to completion even if one Mono failed. AllDtos allDtos = Mono. zipDelayError (Arrays. asList (firstDto , secondDto , (Mono&l
Read more

Spring Boot Reactive API Part 2

Image
 Spring Boot Reactive: Improving CPU bound performance using Scheduler In part 1 , we have seen that Spring Boot Reactive doesn't really improve performance if the WAITING time is CPU bound / CPU intensive tasks. This article show a quick way on how we can improve the speed through specific configuration Setup Spring Boot's embedded Tomcat is reconfigured to only use 10 worker threads, this way we can clearly see the performance limitation and tweaks. Gatling is configured to simulate 30 concurrent requests with 30000 milliseconds request timeout. APIs internal process is calling java native code that calculate the value of PI over 1 million iterations Default / No scheduler The main reason why CPU bound tasks do not improve (or even degrade) with high parallelism is because of the costly overhead for context switching in the low level. In the scenario below, 10 main threads are all being used to calculate PI values and because there are less CPU than threads, a lot of context
Read more