I think they already did. From TFA:
Sometimes the hype tends to pan out and concepts such as âoee-commerceâ become a normal way to shop.
60% of the time, it works every time.
Either way, the term âoesoftware definedâ is with us to stay, and there is real meaning and value behind it if you look past the hype.
Except that the term "software defined" is not itself defined except by whatever marketing department wants to make it fit their product.
And the term will eventually be replaced with another marketing term.
Just as SaaS replaced ASP.
Just as ASP replaced thin-client.
What all these âoesoftware-definedâ concepts really boil down to is: Virtualization of the underlying component and accessibility through some documented API to provision, operate and manage the low-level component.
Which means that you'll only have the access and granularity that the API gives you.
And somewhere, someone will have to deal with the real servers and switches and such. And to him, you'll just be another account in a bunch of accounts. Sure, they'll deduct the cost of your downtime from your next bill. Well, the cost of what you pay them per business hour per business day.
Don't like it? Just try to get your data from them so that you can move it to a different provider.
And each provider will be under the same pressures to reduce costs as much as possible in order to maximize their profits.