wood burning stoves 2.0*
The moose likes Meaningless Drivel and the fly likes .NET or J2EE Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Other » Meaningless Drivel
Bookmark ".NET or J2EE " Watch ".NET or J2EE " New topic
Author

.NET or J2EE

forums UseR
Ranch Hand

Joined: Feb 24, 2009
Posts: 169

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
Bartender

Joined: Oct 14, 2005
Posts: 18129
    
    8

Either. But are you sure you meant to post this in the Meaningless Drivel forum?
forums UseR
Ranch Hand

Joined: Feb 24, 2009
Posts: 169
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

Joined: Aug 16, 2005
Posts: 13875
    
  10

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.


Java Beginners FAQ - JavaRanch SCJP FAQ - The Java Tutorial - Java SE 7 API documentation
Scala Notes - My blog about Scala
marc weber
Sheriff

Joined: Aug 31, 2004
Posts: 11343



"We're kind of on the level of crossword puzzle writers... And no one ever goes to them and gives them an award." ~Joe Strummer
sscce.org
Pat Farrell
Rancher

Joined: Aug 11, 2007
Posts: 4637
    
    5

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

Joined: Jul 26, 2007
Posts: 9990
    
    7

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?


[How to ask questions] [Donate a pint, save a life!] [Onff-turn it on!]
Pat Farrell
Rancher

Joined: Aug 11, 2007
Posts: 4637
    
    5

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

Joined: Feb 24, 2009
Posts: 169
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!
 
wood burning stoves
 
subject: .NET or J2EE
 
Similar Threads
Java is lossing jobs to .net
JavaRanch versus theServerSide
Sun, Microsoft settle suit in billion-dollar pact
J2EE or .NET
new to J2EE