Linked by Eugenia Loli on Fri 28th Jul 2006 18:28 UTC
.NET (dotGNU too) Microsoft is leaving Java in the dust, but the company still has room to grow in the developer arena, a key executive said. Speaking at the Microsoft FAM (Financial Analyst Meeting) on July 27 in Redmond, Wash., Bob Muglia, Microsoft's senior vice president of Server and Tools business, said Microsoft's .Net platform has outpaced Java, particularly the Java Enterprise Edition, over the past five years to become the development platform of choice for enterprise development.
Thread beginning with comment 147612
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: .NET in the enterprise??
by zambizzi on Sun 30th Jul 2006 17:07 UTC in reply to "RE[4]: .NET in the enterprise??"
Member since:

I'm not sure that's a valid comparison. The application I spoke of was *quite* large and had several very complicated features requiring some very gnarly SQL to perform. One might say there was a design problem but as w/ all RDBMS-based solutions - you can't constantly change your data-model to adapt to every use-case as the system grows and changes in use.

Eventually we moved some of the features that turned out to be *mostly* read-only and that had very large queries to Crystal Reports, leaving the editing features in place. The performance increased considerably on those features. At the warehouse there were several PocketPC based applications used to scan and track inventory - as the folks at the warehouse got busier and busier, the system dragged on even further...making the web users suffer even more.

I'm not sure you can compare the portal solution you mention w/ the application we dealt with - I'd dare say the complexity level was many times more in comparison.

Aside from performance problems, a system based on copious amounts of ADO.NET data-access code, stored procedures, and ASP.NET turned out to be highly resistent to change. It was not fun to change & maintain as it grew. However, these problems went away as we moved to an EJB3-based solution w/ JPA. It performs and changes can be made many times easier.

Reply Parent Score: 1