4 ms·
Fargate does not use Firecracker, it is simply ec2 instances.
by baxter_pad 3mo ago
Fargate does not use Firecracker, it is simply ec2 instances.
- eyjafjallajokul 3mo agoSource? https://aws.amazon.com/blogs/aws/firecracker-lightweight-virtualization-for-serverless-computing/ https://aws.amazon.com/blogs/aws/firecracker-lightweight-vir... says > Battle-Tested – Firecracker has been battled-tested and is already powering multiple high-volume AWS services including AWS Lambda and AWS Fargate.
- baxter_pad 3mo agothe doc is out of date
- easton 3mo agoCounterpoint: https://justingarrison.com/blog/2024-02-08-fargate-is-not-firecracker/ https://justingarrison.com/blog/2024-02-08-fargate-is-not-fi... And also, you’ll notice that Fargate takes minutes to launch while Lambda takes a second or less. You’re waiting on AWS to launch a EC2 with your config and pull your containers into it. (that article matches things I heard from Amazon when I asked why my stuff is slow)
- everfrustrated 3mo agoContainer pulls are slow. Lambda starts fast as it's not unpacking your container to a local disk on every start.
- luhn 3mo agoI can't tell you why Fargate is so slow, but the reason Lambda containers are so fast is because it doesn't actually load the image. It loads a manifest of the layers and the files in each, and then each file is loaded on-demand from a multi-tier cache. 90% of the image is never loaded, and 90% of the remainder is served from local cache. It's a pretty cool architecture.
- binsquare 3mo agoConfirming, I worked directly on fargate. Fargate does not use firecracker. It was used for some internal workloads but was being migrated off at the end of 2025.
- my123 3mo agoIt was true a long time ago for some particular cases, but is not true since quite some years now.
- alFReD-NSH 3mo agohttps://aws.amazon.com/blogs/aws/firecracker-lightweight-virtualization-for-serverless-computing/ https://aws.amazon.com/blogs/aws/firecracker-lightweight-vir...