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

Docker

169.9K
136.5K
+ 1
3.9K
Webpack

39.9K
27K
+ 1
752
Add tool

Docker vs Webpack: What are the differences?

Introduction

This Markdown code provides a comparison between Docker and Webpack, highlighting the key differences between the two technologies.

  1. Containerization vs. Module Bundling: The primary difference between Docker and Webpack lies in their core functionalities. Docker is a containerization platform that allows applications to run in isolated environments called containers, while Webpack is a module bundler primarily used for JavaScript applications.
  2. Application Deployment vs. Development: Docker focuses on application deployment, providing a consistent and reproducible environment for running applications. On the other hand, Webpack is primarily used in the development phase to bundle JavaScript modules and optimize assets for efficient delivery to the browser.
  3. Isolation vs. Optimization: Docker containers provide application isolation by packaging the entire environment, including the operating system and dependencies, into a single unit. In contrast, Webpack optimizes files by analyzing dependencies and creating an optimized build for efficient serving to the client, without providing application isolation.
  4. Scalability and Portability: Docker enables easy scaling by allowing multiple containers to be run across different hosts, making it suitable for distributed systems. Webpack, on the other hand, is not specifically designed for scaling and is mainly used within the context of a single application or project.
  5. Runtime Overhead: Docker containers carry additional runtime overhead due to the need to run a separate operating system and manage isolation. This can result in heavier resource usage compared to using Webpack, which performs optimizations at the build stage and does not introduce additional runtime overhead.
  6. Use Cases: Docker is commonly used for deploying complex applications with multiple services, enabling smooth collaboration between development and operations teams. Webpack, on the other hand, is popular for bundling JavaScript modules and assets for web development projects, optimizing performance and improving development workflows.

In summary, Docker and Webpack serve different purposes in the software development lifecycle, with Docker focusing on application deployment and isolation through containerization, while Webpack is primarily used for bundling JavaScript modules and optimizing assets during development.

Decisions about Docker and Webpack
Aleksandr Filatov
Contract Software Engineer - Microsoft · | 4 upvotes · 281K views
Why migrated?

I could define the next points why we have to migrate:

  • Decrease build time of our application. (It was the main cause).
  • Also jspm install takes much more time than npm install.
  • Many config files for SystemJS and JSPM. For Webpack you can use just one main config file, and you can use some separate config files for specific builds using inheritance and merge them.
See more

We mostly use rollup to publish package onto NPM. For most all other use cases, we use the Meteor build tool (probably 99% of the time) for publishing packages. If you're using Node on FHIR you probably won't need to know rollup, unless you are somehow working on helping us publish front end user interface components using FHIR. That being said, we have been migrating away from Atmosphere package manager towards NPM. As we continue to migrate away, we may publish other NPM packages using rollup.

See more
Florian Sager
IT DevOp at Agitos GmbH · | 3 upvotes · 415.2K views
Chose
LXDLXD
over
DockerDocker

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 StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Docker
Pros of Webpack
  • 823
    Rapid integration and build up
  • 691
    Isolation
  • 521
    Open source
  • 505
    Testa­bil­i­ty and re­pro­ducibil­i­ty
  • 460
    Lightweight
  • 218
    Standardization
  • 185
    Scalable
  • 106
    Upgrading / down­grad­ing / ap­pli­ca­tion versions
  • 88
    Security
  • 85
    Private paas environments
  • 34
    Portability
  • 26
    Limit resource usage
  • 17
    Game changer
  • 16
    I love the way docker has changed virtualization
  • 14
    Fast
  • 12
    Concurrency
  • 8
    Docker's Compose tools
  • 6
    Easy setup
  • 6
    Fast and Portable
  • 5
    Because its fun
  • 4
    Makes shipping to production very simple
  • 3
    Highly useful
  • 3
    It's dope
  • 2
    Very easy to setup integrate and build
  • 2
    HIgh Throughput
  • 2
    Package the environment with the application
  • 2
    Does a nice job hogging memory
  • 2
    Open source and highly configurable
  • 2
    Simplicity, isolation, resource effective
  • 2
    MacOS support FAKE
  • 2
    Its cool
  • 2
    Docker hub for the FTW
  • 2
    Super
  • 0
    Asdfd
  • 309
    Most powerful bundler
  • 182
    Built-in dev server with livereload
  • 142
    Can handle all types of assets
  • 87
    Easy configuration
  • 22
    Laravel-mix
  • 4
    Overengineered, Underdeveloped
  • 2
    Makes it easy to bundle static assets
  • 2
    Webpack-Encore
  • 1
    Redundant
  • 1
    Better support in Browser Dev-Tools

Sign up to add or upvote prosMake informed product decisions

Cons of Docker
Cons of Webpack
  • 8
    New versions == broken features
  • 6
    Unreliable networking
  • 6
    Documentation not always in sync
  • 4
    Moves quickly
  • 3
    Not Secure
  • 15
    Hard to configure
  • 5
    No clear direction
  • 2
    Spaghetti-Code out of the box
  • 2
    SystemJS integration is quite lackluster
  • 2
    Loader architecture is quite a mess (unreliable/buggy)
  • 2
    Fire and Forget mentality of Core-Developers

Sign up to add or upvote consMake informed product decisions

What companies use Docker?
What companies use Webpack?
See which teams inside your own company are using Docker or Webpack.
Sign up for StackShare EnterpriseLearn More

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

What tools integrate with Docker?
What tools integrate with Webpack?

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

What are some alternatives to Docker and Webpack?
LXC
LXC is a userspace interface for the Linux kernel containment features. Through a powerful API and simple tools, it lets Linux users easily create and manage system or application containers.
rkt
Rocket is a cli for running App Containers. The goal of rocket is to be composable, secure, and fast.
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.
Cloud Foundry
Cloud Foundry is an open platform as a service (PaaS) that provides a choice of clouds, developer frameworks, and application services. Cloud Foundry makes it faster and easier to build, test, deploy, and scale applications.
Vagrant
Vagrant provides the framework and configuration format to create and manage complete portable development environments. These development environments can live on your computer or in the cloud, and are portable between Windows, Mac OS X, and Linux.
See all alternatives