Continuous delivery, company-wide hackathons, growth hacking, features driven by user feedback through sites like user voice: The new face of Microsoft is all about moving faster and being more responsive. Moving faster can also mean things breaking. But failure, and what you do when things go wrong, look rather different in a cloud-first mobile-first world.
Two weeks ago, Amazon announced its quarterly earnings, reporting a much larger net loss than expected. There was much speculation by pundits about the reasons for the scale of the loss (including me in a CNBC segment). Many commentators placed responsibility for size of the loss on Amazon Web Services -- after AWS responded to an approximately 30 percent price cut by Google, the size of the "other" AWS category, in which Amazon places AWS revenues, fell 3 percent from the previous quarter.
Horror stories don't just happen at the movie theater. In a few cases, companies make a big play to use the wrong cloud application or experience widespread outages in their connection to cloud storage.
In August 2012, SAIC, the $11B national security, engineering, and enterprise IT provider, announced that it would split in two: SAIC would deliver enterprise IT services to the government sector, and a new company, Leidos, would provide services in security, health and engineering.
Moving virtual servers around a hybrid cloud environment isn't hard, but managing the data is. That's why NetApp wants to be "the enterprise data-management standard across the enterprise," says CEO Tom Georgens. Network World Editor in Chief John Dix recently caught up with Georgens to get his take on what changes in the cloud computing world.
My last couple of columns have addressed cloud adoption patterns by IT organizations. Has Cloud Computing Been A Failed Revolution discussed the seeming ennui regarding cloud computing on the part of IT groups a that they seem less interested in the field, despite the belief on the part of vendors that the cloud represents tomorrow's technology infrastructure. Most recently, The Real Cloud Computing Revolution described three real-world examples of companies using cloud computing to solve problems they couldn't have addressed in the infrastructure models of traditional IT.
Sure, the enterprise push by Apple and IBM should worry the Android camp, and business writers should make sure they have an up-to-date obituary ready for BlackBerry. But Microsoft is the company with the most to lose.
As recently as five years ago, setting up a new business and equipping it for a PC-literate workforce was a costly affair. You needed to acquire server hardware and pay various software licensing fees.
Two weeks ago, venerable media company CondA(c) Nast -- publisher of magazines like Vogue, The New Yorker and Wired -- decommissioned its Newark, Del. data center. The 67,200 square feet facility had already been sold and the deal closed. The 105-year-old company had gone all-in with the cloud.
When it comes to budgeting for cloud software, it's important to have some solid data about the cost of deploying a "zero-feature" update, the likelihood of encountering latent bugs, and the level of effort required for simple developer overhead and housekeeping. While there's some good data and solid advice out there from the Standish Group, as I mentioned in a recent article, I haven't seen any data that's particularly modern or really focused on the harsh realities of cloud software development.
Can you name a single activity that consumes more IT staff time and presents more potential exposure to enterprise security risks than maintaining desktop and laptop computers across the enterprise? Despite the widespread use of remote desktop management tools, administrators must periodically descend upon offices and cubicles to upgrade or troubleshoot PCs.
This paper outlines the challenges and obstacles to successful implementation, and discusses existing, rapid-deployment solutions for connecting pop-up locations with mission-critical retail applications...