Docker vs Webpack: What are the differences?
What is Docker? Enterprise Container Platform for High-Velocity Innovation. 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.
Docker belongs to "Virtual Machine Platforms & Containers" category of the tech stack, while Webpack can be primarily classified under "JS Build Tools / JS Task Runners".
"Rapid integration and build up", "Isolation" and "Open source" are the key factors why developers consider Docker; whereas "Most powerful bundler", "Built-in dev server with livereload" and "Can handle all types of assets" are the primary reasons why Webpack is favored.
Docker and Webpack are both open source tools. Docker with 53.8K GitHub stars and 15.5K forks on GitHub appears to be more popular than Webpack with 49.5K GitHub stars and 6.22K GitHub forks.
Lyft, StackShare, and Shopify are some of the popular companies that use Docker, whereas Webpack is used by SendGrid, Sentry, and Yahoo!. Docker has a broader approval, being mentioned in 3471 company stacks & 3322 developers stacks; compared to Webpack, which is listed in 2181 company stacks and 1297 developer stacks.
I could define the next points why we have to migrate:
- Decrease build time of our application. (It was the main cause).
jspm installtakes much more time than
- 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.
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.
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.