Although admins have been free to run Linux containerization technology Docker on top of Amazon Linux running on its rentable EC2 servers for some time, the company on Thursday announced that Docker had been integrated with Elastic Beanstalk. Elastic Beanstalk is a platform-as-a-service technology from Amazon which lets …
If "the cloud" refers to virtualised computing environments, be they private, public or hybrid, then I am a fan.
Containerisation is an incredibly powerful tool for the development and delivery of applications in the virtualised world. Docker appears to have found a way of bringing containerisation into the mainstream. If you haven't looked at it yet, it is worth having a look. https://www.docker.io
For someone with an HTML 2 understanding of web technologies, I cannot for the life of me get my head around what Docker is or how it works. :( Nor can I get my head around what adding it to Amazon Elastic Beanstalk means... I grok a VM. And a "cloud server" is just a VM on a remote machine (like most VMs then). I can run Docker in a VM (so I'm lead to believe). But I can't quite understand from the flowery language what things like Docker and Elastic Beanstalk _actually do_ and why they need to be integrated. I must be a dinosaur.
Docker lets you run an application image on top of a basic Linux kernel; think of it as a 'chroot jail' on steroids. The kernel can be running in a VM or against bare metal.
typical use might be something like a webserver, or a JVM with the associated app code; this gives you isolation from other instances on the same OS with minimum overhead, and reduced resources since they're all sharing the same OS. Should let you get better density on servers.
How may I slice thee, let me count the ways
tl;dr: How may I slice thee, let me count the ways. Simply put, this is platform as a service (PaaS).
Basically, you have four collection layers to play with. Starting from the top, it goes Users <-> Applications <-> Operating System <-> Hardware. Everyone should be familiar with multi-user machines. Here you are slicing things up so each user acts as if the entire machine was theirs and no one else's. That's your basic shared desktop and not too long ago your basic server. The next layer down is where were playing now. That's where you slice up the applications so that each of them, or a given collection of them, thinks that they have an entire operating system when in fact it is shared. This is where you find Docker, chroot jails, Solaris zones, Sandboxie, ThinApp, App-V, even terminal servers really.
In Windows, the result is that an application, or collection of them, has it's own registry, directories, and all the other niggling little details of what an application needs to change when it is installed on a computer but in reality is kept isolated to it's own sandbox. Close the application and foofff, all those changes are gone. As you would expect, especially after the list above, there are a lot of ways you can do this including this new way. Here Amazon is offering cloud (virtual) machines running on Amazon hardware each of which is running cloudy (further virtualised) applications on top. To the user, there's nothing here, move along. To an system administrator, this is rather nice When the user logs on it triggers an assembly process: the users (personalised or not), the user's (personalised or not) applications served up as required, on top of the user's operating system (personalised or not), and lastly the user's (personalised or not) machine. That last one requires a bit of explanation. Some users actually do need a particular hardware set for, say, CAD/CAM, medical imagery, &c.
Where it really shines is that you, hopefully, only need to update only pieces of the above (one particular app, OS...) since the whole thing gets slapped together as it's used which, again hopefully, increases efficiencies at all levels of the stack (users all the way down to hardware). And, by the way, it also makes compliance a bit easier for whoever your dealing with for licenses and such. You get real-time reports on who's using what, where, and when.It's nice enough that I'm contemplating it for our rather strange home-office, at least two firms, one house. [I'm going to commit mayhem on the next person with an EULA that shows up here. Ye Gods, Above and Below!] You can rightfully say "nothing here, move along" except for the fact that each iteration improves things measurably. Docker is newest and rightfully best to date, IMNSHO. [In My Not So Humble Opinion. Everyone who knows me knows I'm not humble.]
- Boffins attempt to prove the UNIVERSE IS JUST A HOLOGRAM
- Review Raspberry Pi B+: PHWOAR, get a load of those pins
- Review Reg man looks through a Glass, darkly: Google's toy ploy or killer tech specs?
- MEN WANTED to satisfy town full of yearning BRAZILIAN HOTNESS
- +Comment 'Stop dissing Google or quit': OK, I quit, says Code Club co-founder