Apps Meet Ops

Everyone's an expert in information technology

Over the past decade, we've heard a lot about the coming consumerization of information technology. Well, it's here. The Web, e-mail, mobile phones, automated teller machines, GPS navigators, supermarket self-checkouts, online banking, digital cameras, instant messaging, chat rooms, online shopping, airline e-tickets, iTunes, YouTube, Facebook--you name it. Every one of them puts large swaths of the population in direct, frequent contact with sophisticated IT systems and interfaces. And this is just the short list.

It's an overstatement to say "everyone's on Facebook" or "everyone has a smartphone"--but not by much. Something like 50 percent of the U.S. population is on Facebook more

The cloud backlash

There's no doubt that the recent "partial failure" of the Amazon Web Services cloud computing platform is giving enterprises, service providers, and developers pause--and will continue to do so for months to come. Amazon called the outage "partial" and a "degradation," but it was a very big deal. A significant part of Amazon's flagship EC2 (Elastic Compute Cloud) was offline for a day, as were the related EBS (Elastic Block Store) and RDS (Relational Database Service) offerings. The failure affected only the northern Virginia data center ("US-East"), and the majority of AWS services continued to run just fine.

Comity (noun):

A state or atmosphere of courtesy, considerate behavior, and mutual respect towards others; harmonious relations.
Friendly understanding and mutual recognition between entities such as corporations, organizations, and nations.
Something increasingly scarce in the IT industry.

IT started as a vertically integrated industry. Companies like DEC and IBM built almost everything from CPUs to application software themselves. But the last 30 years moved IT to a "horizontal" business model. Most vendors built components that would be later integrated by systems vendors, implementation partners, or customers themselves into "the complete solution." The rise of networking and "industry standards" meant that more

Assembling the IT emergency kit

Much of the world is consumed watching the coverage of the enormous disaster that recently struck Japan. As if a massive earthquake and subsequent major tsunami didn't cause enough death and destruction, they unleashed a cascade of failures that led to serious nuclear power plant accidents that have yet to be contained, and that threaten lives and indeed the inhabitability of an entire area of Japan. It's simply horrific.

We humans think that we're in control of, well, everything. We have plans and lists and goals and policies and fallback positions. Then something like this comes along more

Living in a VM world

The big industry event about virtualization is VMworld, usually held in late Summer / early Fall. You don't have to wait for VMware's conference, however, to find yourself in VM World. We now live in it, every day.

It's really quite amazing how quickly virtualization has swept through, and become ensconced in, IT. Data centers have--for decades--been famously conservative when it comes to introducing changes that might threaten to disrupt production applications. For years, whenever we'd ask operationally focused IT managers about introducing new control software--for workload management, service provisioning, automated orchestration, and so on--we always heard more

Network, don't fail me now!

Everything in IT depends on the network.--and not just in an abstract, "need it occasionally" sort of way. The packets must flow for virtually every operation, every job, every transaction. Whenever packets drop, or links go down, we're disconnected and isolated. Information doesn't flow; apps don't work; users don't proceed. We need the network up and running, millisecond by millisecond, every millisecond of every day.

They say you don't really know how valuable a thing is until you miss it and have to do without it. I missed the network a few times this more

Avoiding the cost of entanglement

Modern IT is very focused on economics. We talk endlessly about cost. We debate capital costs vs. operational costs--CAPEX vs. OPEX, in the lingo. We look at Total Cost of Operations (TCO) and we try to calculate our projects' Return On Investment (ROI). But even with all of these economic metrics, we miss an enormous source of costs: Our long-term entanglement with the products, technologies, and approaches we choose.

We choose this platform or database engine or application suite, only to find out a few years later it was overkill, or too expensive, or not as good a fit as

Online word processors: Awesome and primitive

I love that you can now write full, rich, graphical applications for the Web--even for core tools like word processors. As Stephen Shankland recently noted, Google Docs has evolved into something surprisingly useful, even for a professional writer. I second that opinion, and add that competitors like Zoho Writer are similarly powerful, usable, and useful--as are other "Office 2.0" apps for spreadsheets, presentations, project management, and other tasks. Cloud apps have come a long way, baby!

Online editors let you move your work easily to just about any connected computer, and they enormously facilitate live, real-time collaboration. They do more

IT crisis: When the fire truck rolls

I was recently asked to help fix a high-visibility Web site that was performing poorly. I'd like to share some of the lessons--not learned, but reinforced--by the experience.

Fix the problem, not the blame. "We're in trouble! Help!" calls are fraught with embarrassment. Who, after all, wants to admit they have a problem? Many feel they "should" be able to "handle it ourselves," without sending up an emergency flare or asking for assistance. This latest was a straightforward "we can't get decent performance, and it's getting critical!" situation. That shouldn't be too embarrassing. It doesn'more

If virtual desktops great, why not used more?

Virtualization analyst Brian Madden asks an excellent question:

If VDI (virtual desktop infrastructure) is so great, then why aren't you using it?

I'm a bit less skeptical. Here's why:

Maturity - There have been an awful lot of technologies that labored years to achieve a level of capability, completeness, and maturity needed for them to really take hold. The Internet, for example. You know--that thing most of us now don't know how to live without? Inter-networking was born in the early 1970s, but it wasn't until about 1995 that it really took off. When it