Automating the world one-liner at a time…
Today is Partner day at MMS where we have special sessions focused to the special needs of ISV and IHVs. I'll be giving an 1.5 hour talk: System Center Foundation Technologies in which I discuss the management technologies that ship in Windows that the System Center products build upon.
Most, but not all, System Center products have been shipping for quite a long time so it presents a bit of challenge. Whenever an new technology comes out, retrofitting an existing product to leverage it is a complex equation. You might think that as soon as a new platform technology becomes available, products leap at the opportunity to convert to using it. After all you get:
Seems like a no-brainer right? Hardly. The team has to factor that against:
Then you have to consider the startups. Startup efforts have no existing code and have a PASSION of leveraging other peoples code (thus incurring all the benefits of the first list) and catapulting themselves to new levels of competition by writing the code that they and only they could write. Leveraging the platform technologies means that every turn of the crank puts them at greater and greater levels of functionality with little to no costs while they get to focus on truly competitive features. In the meantime, their competition that didn't pick up the new technology is spending the time and effort fixing bugs, duplicating features or falling behind.
Turn the crank once and there adopters have improved by a bunch and the non-adopters haven't. It is uncommon (but not unheard of) for one turn of the crank to produce a decisive advantage in the marketplace. There are too many other factors in the equation. But turn that crank a second and a third time and it can be devastating (literally!) [to the competition].
So you might look at all this and ask, "when should a team leverage a platform technology?" That is the question every team must deal with and solve by themselves. Using the platform and NOT using the platform are both bets. You need to look at the details, the upsides/downsides and put your future on the line (pretty good theme given that MMS is being held in Vegas!).
In my talk today, I'll be going through a couple examples of both. I'll discuss Exchange 2007 which retrofitted their existing architecture to take advantage of PowerShell and layer their entire Admin GUI over PowerShell. I'll also discussion SC Virtual Machine Manage (SCVMM) which is a V1 product and was able to leverage a number of the platform technologies our team produces (WMI, BITS, WS-MAN, PowerShell).
If you think SCVMM V1 is awesome, you just wait until we turn the crank on our platform technologies!
Jeffrey Snover [MSFT] Windows Management Partner Architect Visit the Windows PowerShell Team blog at: http://blogs.msdn.com/PowerShell Visit the Windows PowerShell ScriptCenter at: http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx
PingBack from http://adoption.crutoo.com/2008/04/28/dynamics-of-technology-adoption-and-market-competitiveness/