.NET Crashes and Burns
![]() Home
|
It's been a bad week for Microsoft on the Internet. Some say this chain of
events demonstrates Microsoft's inability to manage networks and brings the
viability of their .NET initiative into question. Here's what happened.
AnalysisIF Microsoft is not lying (always a big if), then it's clear they know next to nothing about designing, managing or securing networks. Having all the DNS (Domain Name Service) servers for a worldwide network in one room connected to the Internet through a single router is beyond dumb.Allowing a low level technician to reprogram a critical border router without thorough review and management sign-off is gross negligence. A mistake could cost, well, in this case, $$ billions $$. Taking more than 23 hours to find and correct the problem is simply absurd - either that or it isn't what really happened. Some commentators figure that after this week's demonstration, Microsoft's .NET campaign is dead, because businesses have seen how reliable Microsoft's network is. The point of Microsoft's .NET Initiative is that you will run your business over Microsoft's network, that software is a "subscription service", obtained from Internet servers, and your critical business data will reside on the servers of ASPs (Application Service Providers), not on your own computers. Some commentators feel Microsoft will cancel it's upcoming $250 million .NET advertising campaign for fear it would be treated as a joke. I think they will go ahead - after all, this is the company who's current saturation advertising campaign (featuring a cut-out Blue Screen of Death) rubs in just how crappy the Microsoft products you already own are. There is no anticipation of customer intelligence here. Some commentators feel business will now reject .NET. I disagree. So enamored is business with the concept of "we have no choice" most will embrace .NET. Microsoft is a monopoly precisely because business "decision makers" want to avoid making decisions. .NET will sputter and wheeze and limp along, not because businesses don't accept it, but because it is unworkable. Businesses that embrace .NET will find themselves uncompetitive, but the last thing they will blame is the decision to go with Microsoft. A minority of businesses have already rejected the Microsoft.NET future and are recasting their business systems with Java, thin clients, Unix, Linux and other products compliant with open standards. It is they who will have the competitive advantage. As for Akamai's Microsoft DNS servers running Linux, what do you expect. Akamai does this for a living - they have to use something that works. Andrew Grygus Links
|
©:Andrew Grygus
- Automation Access
- www.aaxnet.com
- aax@aaxnet.com
Velocity Networks:
Network Consulting Service -
Internet Service Provider -
Web Page Design and Hosting
All trademarks and trade names are recognized as property of their owners