I had the pleasure of recording a podcast recently with Battery Ventures Technology Fellow Adrian Cockcroft. Adrian is well known from his days at Netflix and can frequently be seen at major conferences presenting on DevOps, microservices, and cloud computing. Last month, both Adrian and I attended DockerCon in San Francisco. Our conversation started with a discussion about Docker. Continue reading Podcast with Adrian Cockcroft
I had the opportunity to attend Red Hat Summit and DevNation. Nearly every answer to any question at both these events was to “use containers” to solve that problem. While some responses were undoubtedly true, others were not quite as completely true. Yes, you can use containers to solve many problems, but what was often overlooked were the underlying bits of infrastructure necessary to provide the base for the containers. Overall, Red Hat Summit delivered on its promise; I will follow up about DevNation at a later time. Continue reading RedHat Summit: All about Containers
I attended DockerCon 2015 this week in San Francisco. I have been writing about Docker since the days when its name was still dotCloud and it first decided to pull its container technology out of its PaaS solution. I remember the first Docker meetup, which consisted of about five of us in the “jungle” of the original dotCloud headquarters, back in February of 2013. Fast-forward to June 22–23, 2015, and Docker filled up the Grand Marquis in San Francisco and was streaming live to a rabid user base all over the world. Couple that with $190M in funding, and you have a company on fire.
“To Test, or Not to Test,” that is the question. Or more to the point, do we force our customers to be beta testers without asking them, or do we do testing up front as part of our Agile Cloud Development practices? Too often, I feel like I am a beta tester and not the user of a web-scale application. Because we move so fast from coding to production, two things get hammered along the way: real testing, and testing for security! This has got to change, and there is a way. Continue reading To Test, or Not to Test
Elliott Management has a plan for Citrix. Shake out sales and marketing, sell GoTo and NetScaler, dump the dead wood, and shut down all blue-sky research. There has been no response yet from Citrix beyond a brief note to say “we’ll get back to you on that,” but you can bet that CEO Mark Templeton will not look favorably on the proposal. Regardless of how Templeton feels, with Elliott in play, Citrix has to make changes. What, then, are the choices that Citrix can make?
Containers are all the rage these days. Many large enterprises are experimenting with containers, and some have implemented them in some form or fashion. Most of the excitement and experimentation is a grassroots effort, and containers are being used within pockets of the enterprises. In many cases, management is aware of container technology but has not yet bought into an all-out container strategy. Some of the hesitation that I hear from C-level executives is that containers are not mature enough yet, containers have security gaps, there is a lack of skills and training, and they don’t want to give up their investment in VMs. The practitioners who are implementing containers see huge opportunities in agility, quality, portability, and manageability. So, how can we explain the value of containers to our bosses so we can get broader adoption of a technology that can solve a lot of business problems?