Need advice about which tool to choose?Ask the StackShare community!

AWS Firecracker

6
25
+ 1
0
Docker

102.7K
81.4K
+ 1
3.8K
Add tool
Decisions about AWS Firecracker and Docker
Florian Sager
IT DevOp at Agitos GmbH · | 2 upvotes · 176.4K views
Chose
LXD
over
Docker

lxd/lxc and Docker aren't congruent so this comparison needs a more detailed look; but in short I can say: the lxd-integrated administration of storage including zfs with its snapshot capabilities as well as the system container (multi-process) approach of lxc vs. the limited single-process container approach of Docker is the main reason I chose lxd over Docker.

See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of AWS Firecracker
Pros of Docker
    Be the first to leave a pro
    • 821
      Rapid integration and build up
    • 688
      Isolation
    • 517
      Open source
    • 504
      Testa­bil­i­ty and re­pro­ducibil­i­ty
    • 459
      Lightweight
    • 217
      Standardization
    • 182
      Scalable
    • 105
      Upgrading / down­grad­ing / ap­pli­ca­tion versions
    • 86
      Security
    • 84
      Private paas environments
    • 33
      Portability
    • 25
      Limit resource usage
    • 15
      I love the way docker has changed virtualization
    • 15
      Game changer
    • 12
      Fast
    • 11
      Concurrency
    • 7
      Docker's Compose tools
    • 4
      Fast and Portable
    • 4
      Easy setup
    • 4
      Because its fun
    • 3
      Makes shipping to production very simple
    • 2
      It's dope
    • 1
      Highly useful
    • 1
      MacOS support FAKE
    • 1
      Its cool
    • 1
      Docker hub for the FTW
    • 1
      Very easy to setup integrate and build
    • 1
      Package the environment with the application
    • 1
      Does a nice job hogging memory
    • 1
      Open source and highly configurable
    • 1
      Simplicity, isolation, resource effective

    Sign up to add or upvote prosMake informed product decisions

    Cons of AWS Firecracker
    Cons of Docker
      Be the first to leave a con
      • 7
        New versions == broken features
      • 4
        Unreliable networking
      • 4
        Documentation not always in sync
      • 3
        Moves quickly
      • 1
        Not Secure

      Sign up to add or upvote consMake informed product decisions

      What is AWS Firecracker?

      Firecracker is an open source virtualization technology that is purpose-built for creating and managing secure, multi-tenant container and function-based services that provide serverless operational models. Firecracker runs workloads in lightweight virtual machines, called microVMs, which combine the security and isolation properties provided by hardware virtualization technology with the speed and flexibility of containers.

      What is Docker?

      The Docker Platform is the industry-leading container platform for continuous, high-velocity innovation, enabling organizations to seamlessly build and share any application — from legacy to what comes next — and securely run them anywhere

      Need advice about which tool to choose?Ask the StackShare community!

      What companies use AWS Firecracker?
      What companies use Docker?
      See which teams inside your own company are using AWS Firecracker or Docker.
      Sign up for Private StackShareLearn More

      Sign up to get full access to all the companiesMake informed product decisions

      What tools integrate with AWS Firecracker?
      What tools integrate with Docker?

      Sign up to get full access to all the tool integrationsMake informed product decisions

      Blog Posts

      +7
      3
      654
      +14
      11
      2039
      Jul 9 2019 at 7:22PM

      Blue Medora

      +8
      11
      1731
      +8
      6
      2190
      +17
      32
      28669
      What are some alternatives to AWS Firecracker and Docker?
      Kubernetes
      Kubernetes is an open source orchestration system for Docker containers. It handles scheduling onto nodes in a compute cluster and actively manages workloads to ensure that their state matches the users declared intentions.
      AWS Lambda
      AWS Lambda is a compute service that runs your code in response to events and automatically manages the underlying compute resources for you. You can use AWS Lambda to extend other AWS services with custom logic, or create your own back-end services that operate at AWS scale, performance, and security.
      Serverless
      Build applications comprised of microservices that run in response to events, auto-scale for you, and only charge you when they run. This lowers the total cost of maintaining your apps, enabling you to build more logic, faster. The Framework uses new event-driven compute services, like AWS Lambda, Google CloudFunctions, and more.
      Azure Functions
      Azure Functions is an event driven, compute-on-demand experience that extends the existing Azure application platform with capabilities to implement code triggered by events occurring in virtually any Azure or 3rd party service as well as on-premises systems.
      Cloud Functions for Firebase
      Cloud Functions for Firebase lets you create functions that are triggered by Firebase products, such as changes to data in the Realtime Database, uploads to Cloud Storage, new user sign ups via Authentication, and conversion events in Analytics.
      See all alternatives