Those of you who have perused my blog last year (or talked to me in person) know that I’m pretty stoked about containers. I think they are very cool conceptually and can bring a lot of value to streamlining the development process.
AWS has several options for containers and I wanted to do a VERY high level run through these to distinguish them a bit and maybe whet your appetite to dive into them a little more.
My first session at VMworld 2017 was “What’s New and What’s Next for VMware Cloud Management Platform.” There are a ton of great sessions and overlap at this conference, but I thought this would be a good one to attend (and blog on) as they touched on a lot of things VMware is doing outside of itself.
A big issue in the tech field today is that the world is moving “open.” Open source, open APIs, commodity hardware, etc. Customers are very wary of vendor lock-in that prevents them from either using new solutions or moving to other solutions later.
VMware has clearly recognized this, as a primary focus of late is cloud and product interoperability. This is huge for a massive company like VMware who has TONS of proprietary stuff. Continue reading
If you have been under a rock (like I was for a while!), Docker is a container technology and containers are very cool. Containers sparked my interest in the same way that virtualization did the first time I saw it. I really regret not getting into it sooner but better late than never. Seriously if you haven’t played with containers at all try it on a local system, VM, or use this really nifty site http://training.play-with-docker.com/
raid-zero.com 