good description…
sribe
henry-hz
they could let us to send only a beam file, with the function, creating a web view of the hot-upgrade process, so latency would comeback to soft-real time, and they would save a lot of resources.
1
mkunikow
But I think the problem is general languages on VM.
Now java has https://www.graalvm.org/. So if you want to create lambda function using java you run first code from Gral VM and you have fast startup time. Cloud is moving from long running processes to fast kill fast start.
3
neobats
This was a helpful introductory comment into serverless and specifically lambda. I’m highly unfamiliar with the architecture, and reading through this was very informative. Thank you!
0
benkeil
cblavier
AWS has just announced SnapStart which starts your app after deployment, takes a snapshot of the disk + memory at that time, and then spawns very quickly an already initialized application.
This looks like a good solution to the BEAM slow start time shortcomings aforementioned in this topic.
Do you think we can leverage this with Elixir?
6
StorageCluster
Cross Posting for visibility from Elixir on AWS Lambda? Or more broadly: Elixir as a Service
there has been an update on the Elixir “native” on AWS Lambda. There is a project by (I think @bmalum) called Mayfly - just discovered it on https://elixir-aws-lambda.dev works well, no Hex Package yet.
1