Feedback: The Move from J2EE
On Tuesday, I wrote
about BMC's new Application Problem Resolution System 7.0 tooling, which provides
"black box" monitoring and analysis of application behavior to help
In talking to BMC Director Ran Gishri, I ran across some interesting perspectives
that he was able to offer on the enterprise development space. Among them, the
fact that large orgs seem to be moving away from J2EE and toward a mix of .NET
and sundry lightweight frameworks.
Richard Eaton, an RDN reader who's a manager of database systems for
Georgia System Operations Corp., confirms Gishri's insights. He wrote:
"In 2003, we made a decision to build our Web application using Java
and a third-party RAD tool for Java development that was locally supported
at that time. Since then, the company that developed and supported that RAD
tool has gone out of business and left us with virtually no support for the
product. The application development that was done was very integrated into
the tool, which meant we would virtually have to rewrite the entire app. So
we analyzed our experience with using Apache, Linux, Java and Eclipse for
our platform and realized the effort was very management-intensive for our
small team, and so we looked to .NET.
"Considering the advances in the .NET framework and CLR libraries
and the integration it offered to our other third-party tools, as well as
our prolific Excel spreadsheet environment, the decision was easy to go to
.NET. We are also moving away from Sybase databases to SQL Server and looking
into the use of SharePoint for various internal collaboration and project
functions. The one-stop shop of Microsoft technology and support and ease
of development and integration, I think, is the overwhelming weight in deciding
between J2EE and .NET."
Are you seeing a shift away from J2EE in enterprise development? Tell us your
perspective at firstname.lastname@example.org.
Posted by Michael Desmond on 05/01/2008 at 1:15 PM