holy-lambda VS upx

This is easily accessible via https://github.com/FieryCod/holy-lambda

https://github.com/FieryCod/holy-lambda + free tier may fit your needs. Also support for babashka or scittle in lambdas. Many options. Looks like every provider has caught up to the cloud function space, so aws, azure, digital ocean, maybe even linode. Maybe shop around.

Check https://github.com/FieryCod/holy-lambda. It supports Clojure, babashka and native.

I'm running Clojure code compiled with GraalVM native for AWS Lambda. Cold start times are low and performance is decent enough, even with CE edition. The whole process is reasonably painless through the use of Holy Lambda https://github.com/FieryCod/holy-lambda

Not quite what you were asking for, but I wanted to chip in as another happy Clojure + GraalVM native user.

This is why holy-lambda-ring-adapter was released. An adapter is a part of holy-lambda project and is already used in production. The adapter supports all the holy-lambda custom backends:

During the weekend I was experimenting with AWS Polly (which is a text-to-speech AWS service) and Babashka in order to demonstrate usage of holy-lambda (a micro framework for running Clojure on the AWS Lambda).

It's my first post here announcing holy-lambda https://github.com/FieryCod/holy-lambda. I've resisted posting it for almost two years since it was far from being production-ready software. On the other hand, today, holy-lambda reached version 0.1.45 with some great features and fixes included. It's high time to show this project publicly.

According to this source:

Following optimization, tools like UPX can compress the resulting binary, significantly reducing file size. This compression is invaluable for resource-constrained environments but adds a decompression step during binary execution.

I have been using UPX but I'm quite sure if there's something out there that offers better compression.

Ah that's nice, long ago I used parchment.js to load a inform7 created z5 file on my website. You could try to compress your executable with upx https://upx.github.io/

In this process, the given packer tool embeds a natively compiled PE into another executable that contains the information needed to unpack the original content and execute it. Perhaps the most well known packer, which is not even for malicious purposes, is Golang's UPX package.

Rewrite in C#, and use an obfuscator on the DLL. You can also write some parts in C++ as many variable and function names are forgotten when compiling. You should also encrypt the PCK, and see if you can embed it. If it's embedded, you can make it more annoying to deal with by packing it with https://upx.github.io/

Another good example of false positives like this would be binaries that are compressed with UPX - the way it works is apparently very similar to how stub-loader malware operates and signature detection tools will flag it as malicious.

This will optimise the release binary to be as small as possible. Additionally with upx we can create really small docker image !

Then I compressed it with upx, cp small.exe smallUpx.exe && upx --brute smallUpx.exe, got a 10752 bytes executable, half the size, but still pretty large