Given unlimited money and time and asked to develop a J2EE based application, which app server will you choose?
What will be your approach in developing the app?
Constraints:
1) You need to connect to a legacy system.
2) You need to scalable.
-
App Server Choice (7 messages)
- Posted by: Anil Saldhana
- Posted on: April 25 2003 17:52 EDT
Threaded Messages (7)
- JBoss by Michael Niessner on April 25 2003 21:24 EDT
- WebLogic by Aaron Robinson on April 27 2003 13:48 EDT
- App Server Choice by JT Wenting on April 28 2003 04:25 EDT
- App Server Choice by Aaron Robinson on April 28 2003 08:26 EDT
- App Server Choice by Anil Saldhana on April 28 2003 11:16 EDT
- App Server Choice by Aaron Robinson on April 28 2003 08:26 EDT
- App Server Choice by Anil Saldhana on April 28 2003 11:19 EDT
- Re: App Server Choice by Alan Choy on April 28 2003 11:27 EDT
-
JBoss[ Go to top ]
- Posted by: Michael Niessner
- Posted on: April 25 2003 21:24 EDT
- in response to Anil Saldhana
JBoss. -
WebLogic[ Go to top ]
- Posted by: Aaron Robinson
- Posted on: April 27 2003 13:48 EDT
- in response to Anil Saldhana
As good as I'm sure JBoss is, it is largely unproven in the enterprise. WebLogic has the biggest market share, probably because it is usually far more up to speed with the specs and is already being used in many live systems and so is a proven product.
Of course, if this doesn't work for you, you can just try one of the other app servers, because you have unlimited time and money. -
App Server Choice[ Go to top ]
- Posted by: JT Wenting
- Posted on: April 28 2003 04:25 EDT
- in response to Anil Saldhana
With unlimited time AND money, try them all and choose the one you like best :)
I've personally worked on iPlanet, Orion and SilverStream (now Novel eXtend).
I like SilverStream and Orion, iPlanet I didn't care for much.
Stay away from WebSphere, even IBM techs recommended us against it when we mentioned we'd want J2EE compliance (though this was some years ago and things may have improved) plus WebSphere is bloated... -
App Server Choice[ Go to top ]
- Posted by: Aaron Robinson
- Posted on: April 28 2003 08:26 EDT
- in response to JT Wenting
WebSphere is also usually way behind the times. Just look at the tmie between WebLogic supporting full EJB 2.0 and WebSphere catching up. -
App Server Choice[ Go to top ]
- Posted by: Anil Saldhana
- Posted on: April 28 2003 11:16 EDT
- in response to Aaron Robinson
I read an article interview a top IBM J2EE exec in JDJ. He mentioned that the reason why IBM is behind the latest standards in J2EE is that they try to make the product stable/robust for the customers before they bring in new items. -
App Server Choice[ Go to top ]
- Posted by: Anil Saldhana
- Posted on: April 28 2003 11:19 EDT
- in response to Anil Saldhana
Any thoughts on "You need to connect to a legacy system." ???
How will you guys plan to do it?
Keep the discusssion going.... -
Re: App Server Choice[ Go to top ]
- Posted by: Alan Choy
- Posted on: April 28 2003 11:27 EDT
- in response to Anil Saldhana
If you need to connect to a legacy system, I believe JCA (J2EE Connector Architecture) would be the obvious choice to implement. Please visit the following website if you want to learn more about it.
http://java.sun.com/j2ee/connector/