• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

.NET or J2EE

 
forums UseR
Ranch Hand
Posts: 169
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Hello,

If scalability is the focus, which would you choose .NET or J2EE, to re-write a legacy application (that is considerably complex, to today's enterprise standards) ?

Any thoughts are appreciated.
 
Paul Clapham
Sheriff
Posts: 21322
32
Eclipse IDE Firefox Browser MySQL Database
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Either. But are you sure you meant to post this in the Meaningless Drivel forum?
 
forums UseR
Ranch Hand
Posts: 169
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Paul Clapham wrote:Either. But are you sure you meant to post this in the Meaningless Drivel forum?

Your reply proves it so! :)
Although I expected J2EE from you since this is JavaRanch!
 
Jesper de Jong
Java Cowboy
Saloon Keeper
Posts: 15459
42
Android IntelliJ IDE Java Scala Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Note that it has been called Java EE for a while now, and not J2EE. The 2 has been dropped from the name a long time ago.

So no, I wouldn't use J2EE. But I would use Java EE.

You can build scalable systems with either .NET or Java EE, there is no objective answer to whether you should choose one or the other.
 
marc weber
Sheriff
Posts: 11343
Java Mac Safari
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
 
Pat Farrell
Rancher
Posts: 4678
7
Linux Mac OS X VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
srinivas chary wrote: If scalability is the focus, which would you choose .NET or J2EE, to re-write a legacy application (that is considerably complex, to today's enterprise standards) ?


Neither. .NET implies working with Windows, and that rarely is a choice I'd make for scalability or reliability.

J2EE is the devil's spawn. Using it makes me crazy.

Jave EE is OK, but when it has the 2 in it, its evil.

If you don't have to meet some corporate standard, use something like Groovy and Grails.
 
Maneesh Godbole
Saloon Keeper
Posts: 11096
13
Android Eclipse IDE Google Web Toolkit Java Mac Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Whats wrong with the legacy code? Just that it is old and does not follow some modern fangled standards? Was the decision to change made by a committee? Was your boss on that committee? Does he have pointy hair?
 
Pat Farrell
Rancher
Posts: 4678
7
Linux Mac OS X VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Gotta say, @Maneesh Godbole has some good questions here.

My #1 rule is:
if it ain't broke, don't fix it.

Legacy code that works should be left alone.
 
forums UseR
Ranch Hand
Posts: 169
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Maneesh Godbole wrote:Whats wrong with the legacy code? Just that it is old and does not follow some modern fangled standards? Was the decision to change made by a committee? Was your boss on that committee? Does he have pointy hair?


Good questions!

1. Delphi system which is currently stand alone and getting complicated by the day.
2. Tons of fixes, still pending...
3. Lack of Delphi resources.
4. We have Java resource and .NET resource
5. We'd like to web-enable.

Microsoft has been a norm here for a while.


Hope these answer your questions!
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic