programming in java, an two-party IT management software package company, marked in the survey, conveyed by Evans Data Corp. (EDC), that corporate Microsoft .NET investing growth is outpacing Java investing growth. The CA- sponsored survey, which targeted enterprises with 1,000-plus employees and queried 350 software architects and managing directors involved in making and/or managing business-critical Microsoft .NET applications programmes, also observed that a hard market exists for incorporated practical application execution management (APM) solutions that assistance the increased use of both development architectures in the same organization. java api

“These survey resolutions confirm that Microsoft .NET applications programmes are distributive in fundamental enterprises and their acceptance and dependability is continuing to increase,” said Mike Allen, director of product management for CA Wily Technology, a division of CA. “This begs the question of how to effectively manage environments that use both Microsoft .NET and Java. CA Wily advocates a comprehensive practical application execution management solution that addresses both with a single solution and helps key Web practical applications to meet business, customer experience and execution goals.”

The survey observed that most enterprises have highly heterogeneous practical application environments and that Microsoft .NET assistance teams are similar to Java assistance teams in terms of size, structure, problem types and times to isolate problems. A vast majority of respondents said their Microsoft .NET and Java groups are incorporated within their assistance organizations, highlighting the industry requirement for a comprehensive approach to practical application execution management. As with Java, management responsibility is spread across departments (development, operations, quality assurance, etc.), and equally required in both environments.

- java source code Microsoft .NET customers charged connectivity to transactions systems 150 percent more often than Java customers and mainframe connectivity twice as often as Java customers; - Java customers charged bugs 50 percent more often than Microsoft .NET customers; Java customers also charged architecture and JVM (CLR) issues twice as often as Microsoft .NET customers.

- 54 percent of respondents said that development is the department responsible for Microsoft .NET assistance, compared to 69 percent for Java; - Microsoft .NET customers charged changes (both to practical applications and backend connections) for slowdowns 75 percent more often than Java customers did; - Java customers charged memory leaks and out-of-memory conditions 75 percent more often than Microsoft .NET customers, though for slowdown (rather than failure) Microsoft .NET customers blame out-of-memory just as often as Java customers do.

If you enjoyed this post, make sure you subscribe to my RSS feed!