Firecracker – Lightweight Virtualization for Serverless Computing
1–10 of 114 posts
Re: Firecracker – Lightweight Virtualization for Serverless Computing
#2More discussion here: https://news.ycombinator.com/item?id=18539532
Re: Firecracker – Lightweight Virtualization for Serverless Computing
#3What this is allows, and I'm hoping a full fledged service will be announced on Thursday or Friday, is running containers as Lambdas. i.e. if you application starts fast enough, you can just set a container to start and run as a request comes in. It can also shut down when it's done running.
This allows things like per second billing for container runs, serverless containers (there's no container running 24/7, only when there's traffic), etc.
Re: Firecracker – Lightweight Virtualization for Serverless Computing
#4I really hope this helps with the cold start times on Lambda. We were currently looking heavily into moving our API from Lambda to EKS, but if this impacts cold start times, I think we will look at how it ends up looking like in practice.
Re: Firecracker – Lightweight Virtualization for Serverless Computing
#5> Firecracker was built in a minimalist fashion. We started with crosvm and set up a minimal device model in order to reduce overhead and to enable secure multi-tenancy. Firecracker is written in Rust, a modern programming language that guarantees thread safety and prevents many types of buffer overrun errors that can lead to security vulnerabilities.
This is awesome! Really excited to try this out!
Re: Firecracker – Lightweight Virtualization for Serverless Computing
#6This is great. The line between use cases for VM vs container are getting super blurry.
Re: Firecracker – Lightweight Virtualization for Serverless Computing
#7There's a Github Pages FAQ describing why it was made and how it fits with other solutions: https://firecracker-microvm.github.io/
and a high-level design document about how it works https://github.com/firecracker-microvm/firecracker/blob/mast...
Re: Firecracker – Lightweight Virtualization for Serverless Computing
#8What this is allows, and I'm hoping a full fledged service will be announced on Thursday or Friday, is running containers as Lambdas. i.e. if you application starts fast enough, you can just set a container to start and run as a request comes in. It can also shut down when it's done running. This allows things like per second billing for container runs, serverless containers (there's no container running 24/7, only w…
> containers as Lambdas.
How similar is AWS Fargate to what you're describing?
Re: Firecracker – Lightweight Virtualization for Serverless Computing
#9I’m very excited to play with this technology in the same way I love playing with Elixir/Erlang and userland concurrency models. I also love the idea of docker (and use it daily) but dislike the ergonomics. My first thought is, particularly with the emphasis on oversubscription, how does the kernel of the host schedule work?
Re: Firecracker – Lightweight Virtualization for Serverless Computing
#10What this is allows, and I'm hoping a full fledged service will be announced on Thursday or Friday, is running containers as Lambdas. i.e. if you application starts fast enough, you can just set a container to start and run as a request comes in. It can also shut down when it's done running. This allows things like per second billing for container runs, serverless containers (there's no container running 24/7, only w…
Fargate's entire value proposition is to run containers without provisioning