More interesting, what if you had the means to actually try to meet them?
On the surface, Infrastructure 2.0 seems to have very little value to the end-user. It is, after all, about collaboration at the infrastructure layer. It is under the covers, as it were, of the application blanket with which end-users actually interact. But it may end up that Infrastructure 2.0 will have a direct impact on the control the user has over the way in which applications are delivered. Which is to say they might one day have some. What this means is something along the lines of taking the “choose your download mirror” capability offered by popular download sites and cranking it up about six clicks on the dial. Yes, we’re going to turn it up to eleven. First, let’s lay out some options for these fictional (but very demanding) users:
I value speed and function equally
I value speed over function
I value function over speed
These aren’t your enterprise SLA definitions, granted, but when you’re presenting a user with options that ultimately must be translated into technical terms, you really can’t get too specific. And really, even this level of “SLA” is more than most users have ever had aside from “high bandwidth | low bandwidth” and “big pictures | no pictures”. Besides, this is my post, I’ll define my SLAs any way I want.
Now, how would you go about implementing the means by which such SLAs might be enforced?
If you said “context-aware global application delivery” you’re on the right track. If you added “enabled by Infrastructure 2.0” you get extra points. And a cookie.