As a seasoned Java programmer, usually with Spring Boot, it hurts to learn that most lambdas use JavaScript/TypeScript. What if you want to keep writing your Lambda in Java? A query in google teaches us that Quarkus is the way to go. This blog post introduces Quarkus, GraalVM, and we top it off with AWS CDK to deploy the sample.
Everybody is talking about serverless, and with serverless comes serverless functions. Small pieces of code (in theory) that receive an event (input) and return a message (output). They do not need a server. Therefore they are serverless, and they scale on demand. On the AWS platform, a serverless function is called a Lambda. In theory, you write the code, and AWS takes care of the rest. There is a reason why I put “in theory” in some locations in the text. Even writing the hello world sample does need some authorization configuration, and when running complete Docker images as a lambda, you cannot talk about small pieces of code. Time to focus on typical usage patterns for lambdas.
If there is one thing that I have seen a lot with elasticsearch clusters in the wild, it is problems with security. The out of the box Elasticsearch installation does not have a user_id password protection like most databases do. Using the basic license these days does give you the option, but you still have to configure it yourself. When AWS introduced their AWS Elasticsearch service, it did not configure security out of the box. Therefore Elasticsearch clusters have been famous for exposed data. Check an article like this, but there are lots more. Does this mean Elasticsearch should not be used? No, but you must know what you are doing.