What’s a Box? Is it Like a Container?
I joined Cloud Application Manager in March and this was one of my biggest questions. So what better topic to kick off my blogging career than what a Box is…
Think of a Box as a set of instructions, a DNA, or a blueprint that tells your application components where to go and what to do.
The formal definition: A Box is a reusable, shareable, and portable layer of an application architecture. To create a multi-tier application architecture, you simply stack these Boxes.
Here’s some examples of Boxes and what they do:
- A Java Box contains the necessary files/scripts to install java onto a generic linux image.
- A MongoDB Box makes your database portable and modular. You can also add other variables like database permissions to the Box.
- An NGINX Box allows you to encapsulate your HTTP web server configurations and settings making them reusable for more than one app.
- A Chef Solo Box deploys Chef Solo on your instance and let you run a Chef cookbook.
- A Git Box allows your instance to have an integration with your source code repository which can be used for continuous integration, for example.
So really a Box can be an OS layer, an app...