Institutional knowledge is leaving companies at a rapid rate. Employees are very mobile, moving between companies fairly rapidly. Just as they learn something important, they are out the door. That knowledge is not always transferred to others staying behind. Here one day, gone the next. How can you explain a business decision, technology decision, or any other decision without information? Architects, developers, and business folks should be writing documents to cover all major decisions, but these happen long after the decisions have been made. We lack the reasons behind the decisions, the original questions asked, and all the work leading up to the decisions. We do not want to lose institutional knowledge. Now, into this breach comes a new set of tools.
IT as a Service
IT as a Service (ITaaS) covers private clouds, hybrid clouds, and on-premises clouds, as well as cloud management, including performance management offerings used to create and manage these entities. Consider this IT consumption as a utility. (Read More)
This topic explores Infrastructure as a Service (IaaS) private and hybrid cloud offerings, Platform as a Service (PaaS) private and hybrid cloud offerings, and Software as a Service (SaaS). It also investigates emerging areas such as Desktop as a Service (DaaS), Storage as a Service, and Applications as a Service.
The key areas covered include enterprise applications and use cases that are appropriate for private and hybrid clouds, and how consumers and vendors should select cloud management offerings they will use to manage the various types of cloud services and the journey to the cloud: from A to Z and all points between.
Last week was Oracle OpenWorld. It was held in San Francisco at the Moscone Center, which surprised me. I had thought it was closed for refurbishment, as this was the reason VMware had given for holding its annual US shindig in Las Vegas this year.
It seems like Oracle must always have a public enemy number one. Those of you with long enough teeth will remember spats it has had over the years with Microsoft and, more recently, Google and HPE. Well, it seems that Oracle has a new public enemy in its laser sights, and that is Amazon Web Services (AWS). The OpenWorld keynotes proclaimed that Oracle is now a real cloud player and the fastest growing cloud company out there. However, according to The Register, even the usually docile and compliant conference attendees were quite vociferous in denying this.
Yesterday, after many worries—some regulatory (Would the EU sanction the deal? Would China sanction the deal?), some legal (Were the financial instruments being used to finance the deal unlawful under the US tax code?)—the biggest IT merger ever in terms of monetary value finally occurred. This is one of those landmark occasions. Two of the biggest names in our industry, Dell and EMC2, have merged to become Dell Technologies.
If your company isn’t in the process of implementing Office 365 by this point, there’s a good chance that some IT team members are at least giving it some serious thought. As with many aspects of Microsoft Azure, Microsoft is marketing Office 365 as the ultimate solution—and a good number of CIOs are drinking the Microsoft Kool-Aid without carefully considering some of the finer technical details.
As I think back over the journey from physical, to virtual, to cloud, to containers, there is one technology that stands out—one that has fundamentally moved our mindset away from static resources and has caused a serious shift in how we license, secure, and even think about technology. For me, that shift started the first time I saw vMotion in action (vMotion moves a virtual machine from one host to another without taking the virtual machine down or stopping the running application, and without disaster striking). This one instance shifted my worldview of computing from one in which resources are static to one where they are truly virtual—where the underlying infrastructure in many ways just did not matter. This one technology paved the way for the future of computing.
I recently gave a Bright Talk session on adding security to the Agile Cloud/DevOps Development cycle. Part of this discussion addressed adding security testing as part of the process before, during, and even after continuous deployment. In other words, if we continually deploy, we must continually test. Our testing needs to be in the multi-minded parallel process we use for modern development, not the single-minded pipeline acceptable to most DevOps or agile processes. In the past, a team of people would test, each working independently to improve our software. We need similar capabilities within our automated processes. How do we achieve this? How do we add automated, continual testing? And where can we add this to our process or pipeline?