Unlike the WIN32 application that has been in the past more than 10 years, when your. NET application performance problems can quickly find the crux of the problem? Look at the increasing market share. NET application market, Symantec also need to release a hand to. NET from information security.
. NET in the development efficiency, development platform support is very obvious, but in performance monitoring, high availability in addition to Microsoft has not been able to make people feel monopolistic potential of the solution provider. The reason is manifold, the two-point reason is critical: on the one hand because it is too new, 6 years old and half from 1.0 to 3.5, on the other hand, and the original manufacturer of the relatively weak Java different. NET has been under the strong control of Microsoft, under the combination of MOM, System Center Server and WMI, few vendors are willing to do this market. But relatively general. NET integration and application development, this piece of market potential is huge, as long as it is enough to a certain scale. NET application will consider the operation of monitoring and performance tuning, so see there is such a large "Dongpo meat", Symantec APM (Application Performance Management) department is constantly in the launch of the 8th version of the i3 portfolio.
i3 focus on. NET and SQL Server application, it mainly has two pieces of functionality, for real-time application monitoring of smartlink and performance problems expert system Smarttune, there is also a stand-alone SDK, users can be customized according to the monitoring needs of the monitoring content. Taking into account the large environment of SOA,. NET applications are often "mixed" with Java applications in various IT environments, so this release also includes a knowledge base for the performance diagnostics of EE.
However, whatever "encouraging" evaluations analysts have given to the product, it is believed to be in. NET and SQL Server monitor many of the pressures on the market from Microsoft. After all, the Windows system-level monitoring is almost based on the WMI mechanism, and it's probably not the best one for this mechanism, whether it's learning or practical applications, actually enterprise The library has become a model for many. NET applications, especially for large applications, instrument as the main component of the common block, which can be said to be built for the entire Enterprise Library, its periphery is performance monitor and WMI; The Microsoft Patterns && practices community has been focusing on. NET monitoring and performance tuning, in addition to improving. NET application performance and scalability, monitoring In. NET distributed Application The design and upcoming designing Manageable applications for. NET and other 3 series, the other series will almost always spend a lot of time to explain how to improve. NET application performance, even at the development tools level, the design guidelines for developing Class libraries has been directly embedded in the VSTS development environment. The content is comprehensive, but it seems to give a "half-baked" feeling, for many companies, there is little technical power to string them up, and companies tend to provide business-oriented monitoring capabilities based on a "ready-made" monitoring product, but Microsoft seems to be always committed to its key server products- SQL Server, Shareponint, BizTalk promotion, it can be said that Microsoft left a market, but believe in. NET Manufacturer and enterprise Trust degree The Symantec estimate is also very difficult.
Still, i3 reminds us not only to focus on the white box phase of the code and the operation of the black box system, but also to consider how to turn it into a gray box, otherwise in the IT service today, not running maintenance system support. NET application, it will be as fragile as the last leaf on the branch after winter.