Remove mingw, update README.md

Author: trueangle

README.md

@@ -1,7 +1,27 @@
-#To run local runtime tests using using aws runtime simulator:
-1. Gradlew build ./gradlew build to build lambda executable
-2. Modify docker file to set proper path to lambda function executable
-3. Run docker build -t sample:latest . 
-4. Start server docker run -p 9000:8080 sample:latest
-5. Execute function via curl -XPOST "http://localhost:9000/2015-03-31/functions/function/invocations" -d '{}'
-6. docker ps; docker stop CONTAINER_ID to stop the execution
+# Kotlin Native Runtime for AWS Lambda
+[![Maven Central](https://maven-badges.herokuapp.com/maven-central/io.github.trueangle/lambda-runtime/badge.svg)](https://maven-badges.herokuapp.com/maven-central/io.github.trueangle/lambda-runtime/badge.svg)
+
+A runtime for executing AWS Lambda Functions powered by Kotlin Native, designed to mitigate known
+cold start issues associated with the JVM platform.
+
+Project structure:
+
+- lambda-runtime — is a library that provides a Lambda runtime.
+- lambda-events — is a library with strongly-typed Lambda event models, such
+  as `APIGatewayRequest`, `DynamoDBEvent`, `S3Event`, `KafkaEvent`, `SQSEvent` and so on.
+
+The runtime supports the
+following [OS-only runtime machines](https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html):
+
+- Amazon Linux 2023 (provided.al2023) with x86_64 architecture
+- Amazon Linux 2 (provided.al2) with x86_64 architecture
+
+## Performance
+
+Performance benchmarks reveal that Kotlin Native's "Hello World" Lambda function, executed on Amazon
+Linux 2023 (x86_64) with 1024MB of memory, ranks among the top 5 fastest cold starts. Its
+performance is on par with Python and .NET implementations. For a comparison with other languages (
+including Java), visit https://maxday.github.io/lambda-perf/.
+
+![screenshot](docs/performance_hello_world.png)
+<img src="" alt="Kotlin Native AWS Lambda Runtime benchmarks" width="800"/>

build.gradle.kts

@@ -8,5 +8,5 @@ plugins {
 
 allprojects {
     group = "io.github.trueangle"
-    version = "0.0.1"
+    version = "0.0.2"
 }

docs/performance_hello_world.png

@@ -10,7 +10,6 @@ kotlin {
     macosX64()
     linuxArm64()
     linuxX64()
-    mingwX64()
 
     sourceSets {
         commonMain.dependencies {

lambda-events/build.gradle.kts

@@ -13,7 +13,6 @@ kotlin {
     macosX64()
     linuxArm64()
     linuxX64()
-    mingwX64()
 
     sourceSets {
         commonMain.dependencies {

lambda-runtime/build.gradle.kts

@@ -3,20 +3,14 @@ plugins {
     alias(libs.plugins.kotlin.serialization)
 }
 
-// todo is it a right way to specify main entry point for linux64?
 kotlin {
-    val isArm64 = System.getProperty("os.arch") == "aarch64"
-    val hostOs = System.getProperty("os.name")
-    val isMingwX64 = hostOs.startsWith("Windows")
-    val nativeTarget = when {
-        hostOs == "Mac OS X" -> if(isArm64) macosArm64() else macosX64()
-        hostOs == "Linux" -> if (isArm64) linuxArm64() else linuxX64()
-        isMingwX64 -> mingwX64("native")
-        else -> throw GradleException("Host OS is not supported in Kotlin/Native.")
-    }
-
-    nativeTarget.apply {
-        binaries {
+    listOf(
+        macosArm64(),
+        macosX64(),
+        linuxArm64(),
+        linuxX64(),
+    ).forEach {
+        it.binaries {
             executable {
                 entryPoint = "com.github.trueangle.knative.lambda.runtime.sample.main"
             }
@@ -28,6 +22,8 @@ kotlin {
             implementation(projects.lambdaRuntime)
             implementation(projects.lambdaEvents)
             implementation(libs.kotlin.serialization.json)
+            /*implementation("io.github.trueangle:lambda-runtime:0.0.1")
+            implementation("io.github.trueangle:lambda-events:0.0.1")*/
         }
     }
 }