Virtualization, Containerization and all that Jazz

There's a lot of confusion out there about the terms virtualization, containerization, etc. and the related products such as Vagrant, Docker, VirtualBox, etc. When do I use what?

 I like to think of it this way.



  • The physical machine could be a Mac or a Windows PC or laptop.
  • VirtualBox is an Oracle product that provides the virtualization layer, thereby allowing you (for example) to run Linux on a Windows machine. You can configure the resources (disk, CPU, RAM) you want to allocate to each virtual machine (VM).
  • Vagrant is for consistent environment management paradigms across all platforms/OSs. You can use it to install base software for you application, e.g. the Apache web server.
  • Docker is for containerization and only runs on Linux because it uses Linux's container facility to do its thing.
    • So, it used to be that if you're using Windows, you had to run VirtualBox or some virtualization software to stand up a Linux machine first before you could install Docker.
    • But now Docker comes bundled with a lightweight Linux distribution called Alpine, so you can run it directly on Windows without using VirtualBox.
    • The purpose of containerization is to package up your application code and all of its dependencies (other than the ones covered in the remaining layers of the above diagram).
    • This allows you to run your application (e.g. AEM) in a well-defined, consistent and reliable configuration in an easily/quickly reproducible way across every machine in your team and across all your environments (e.g. QA, UAT, Production, etc.).
    • Containerization is a great solution when you have different applications and/or different versions of the same applications with very different dependencies. For example AEM5.6 and AEM6.5 have very different requirements in terms of which Java versions they support. And typically it's cumbersome to recall and specify those different versions each time you start an AEM instance. It's much easier to define the dependencies in the container once and let the container worry about remembering the details forever after.

Comments

Post a Comment

Popular posts from this blog

Milwaukee Appliance Hand Truck

Image
Milwaukee Appliance Hand Truck, leaning against my shed Also known as a cart or a dolly. The model is HDA700. I paid around $120 for it. Here's a list of the features. Wrought iron frame 800 pound load capacity 6 inch non-marking wheels (solid, non-inflatable, never go flat) Stair climbers to help move loads up and down stairs and curbs Padding to prevent the cart from damaging the appliance (this is the white strip in the picture above) Belt or strap that goes around the appliance to secure it to the cart and keep it in place Manual ratchet belt tightener, the buckle-like part at one end of the belt (more on this below) Belt tightener handle (this is the red handle in the picture above) to add more tension to the belt once the manual ratchet has been used to the tighten the belt  I recently used this hand truck to move a big ass 320 pound refrigerator out of my garage (where it was delivered) and up a couple of steps to the deck, up one more step through the doubl
Read more

My Experiments with the PICAXE 08M2+

Image
PICAXE 08M2+ I generally prefer to do things the hard way. For example, you can either microwave a frozen dinner or cook from scratch. The microwave option is a good backup plan, but cooking from scratch has far too many advantages, as I outlined in a recent blog post on the do-it-yourself way of life. In the electronics and robotics world, the analogy of cooking from scratch is to build circuits using a bare bones micro-controller chip (e.g. the PICAXE ) rather than a fancy board (e.g. the Arduino ). Therefore, once I get a circuit working with the packaged Arduino approach (e.g. this robot I built recently), I usually try to replicate the circuit using more basic components like the PICAXE. My decision to consider the PICAXE was influenced by Charles Platt's coverage of it in his awesome book Make: Electronics . But essentially, I am a minimalist and I want to see how much I can get done with a bare bones chip rather than a bulky board-based micro-controller like the Ar
Read more

Utility trailer buying guide

Image
Introduction I recently bought a utility trailer . (I'll explain momentarily what that is and why you might consider buying one.) Going through the process (research, preparation, purchase, registration, setup and maintenance) has taught me that it's not a simple endeavor and very little good documentation exists in the public domain (e.g. on the Internet). Hence, this post. Research In dictionary terms, of course, "to trail" means "to follow" (or to trace the path of a primary vehicle). Alternately, Wikipedia defines a trailer as an unpowered vehicle pulled by a powered vehicle. So, let's get acquainted with what a utility trailer is and why you might consider buying one. If you're a hardworking, blue collar American you probably already have one -- it's the back half of your pickup truck . Well not quite, but that's the reason Australians refer to a pickup as a utility vehicle. A pickup is characterized by the presence of a flat
Read more