Unlike Win32 applications that have been developed for more than 10 years, when your .NET application has performance problems, can you quickly find the crux of the problem? Looking at the increasing market share of the .NET application market, Symantec also We need to free up one hand for .NET in terms of information security.
.NET's advantages in development efficiency and development platform support are very obvious, but in terms of performance monitoring and high availability, other than Microsoft, there has been no solution provider that can be seen as having monopolistic potential. There are many reasons, but two reasons are key: on the one hand, it is too new and has to go from 1.0 to 3.5 when it is 6 and a half years old; on the other hand, unlike Java, which is relatively weak from the original manufacturer, .NET has always been in Microsoft's Under the strong control of MOM, System Center Server and WMI, few manufacturers are willing to enter this market. However, compared with general .NET integration and application development, this market potential is huge, because as long as the .NET application is of a certain scale, it will consider running monitoring and performance tuning, so seeing that there is such a large "Dongpo "Meat", Symantec's APM (Application Performance Management) department has been launching the 8th version of i3 portfolio so far.
i3 focuses on .NET and SQL Server applications. It mainly has two functions, SmartLink for real-time application monitoring and SmartTune, a performance expert system. It also has an independent SDK so that users can customize monitoring content according to monitoring needs. Considering the general environment of SOA, .NET applications are often "mixed" with Java applications in various IT environments, so this version also includes a knowledge base for J2EE performance diagnosis.
However, no matter what "encouraging" comments analysts give to this product, I believe it will encounter pressure from Microsoft in the .NET and SQL Server monitoring markets. After all, monitoring at the Windows system level is almost based on the WMI mechanism, and the one that best fits this mechanism is probably MOM; whether it is learning or practical application, in fact Enterprise Library has become a model for many .NET applications, especially large-scale applications. As the main component of the Common Block, Instrument can be said to be built-in for the entire Enterprise Library. Its periphery is the performance monitor and WMI; the Microsoft Patterns && Practices community has been paying attention to .NET monitoring and performance tuning, in addition to Improving .NET Application Performance and In addition to the three series of Scalability, Monitoring in .NET Distributed Application Design and the soon-to-be-released Designing Manageable Applications for .NET, almost all other series spend a lot of time introducing how to improve .NET application performance; even at the development tool level , Design Guidelines for Developing Class Libraries have been directly embedded into the VSTS development environment. The content is comprehensive, but it all seems to give people a "half-baked" feeling. For many companies, there is little technical strength to string together the content, and companies prefer to provide oriented solutions based on a "ready-made" monitoring product. The ability to monitor business indicators, but Microsoft seems to be always committed to the promotion of its key server products-SQL Server, SharePonint, and BizTalk. It can be said that Microsoft has left a market, but I believe that there is a gap in the trust between .NET manufacturers and enterprises. Symantec estimates are also tough.
Despite this, i3 reminds us that we should not only pay attention to the code in the white box stage and the black box system in running state, but also consider how to turn it into a gray box. Otherwise, in today's IT service-oriented world, there will be no operation and maintenance system. Supported .NET applications will be as fragile as the last leaf on the branch after winter.