Win a copy of Learn Spring Security (video course) this week in the Spring forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

BEA Weblogic Vs IBM Websphere

 
ss reddy
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello java pundits,

I need your expertise in comparing these two from a developer prospective.
Like market share( current and future), number of developers available in market, chances of getting job as developer or administrator for these products, job competition, pay and future market trends.

I know some of the above are difficult to tell but I need your assumptions and judgment to rate these two. And I greatly appreciate response from each of you.

Thanks
ss reddy

Note: If you found any similar posting please email me the link
 
Lasse Koskela
author
Sheriff
Posts: 11962
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
From a developer's perspective, I'd say WebLogic is all in all easier than WebSphere, but that's coming from someone who's only used WebSphere in one project and the product has probably improved since then (just like WebLogic, of course).
 
Paul Sturrock
Bartender
Posts: 10336
Eclipse IDE Hibernate Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'd second that. I've worked on three projects using WebSphere and its always a far harder environment to work with than Weblogic, and double that on Weblogic. I've always found that (unless you use the complete suite of Websphere tools - WSAD and the likes) you need a far better understanding of the J2EE spec. to try to decode what might be going wrong with your app. I particularaly dislike Websphere's logging architecture - which always felt clunky. Also the command line tool WSAdmin is quite powerful but takes a good while to get used to - and since IBM still have not completely replicated all its functionality in the Admin Console you still need to rely on it now and then. I've also always though BEA do a very good job on their documentation.

Of course that's purely from a developer's point of view, which is almost never the reason why one is picked over the other.
 
Lasse Koskela
author
Sheriff
Posts: 11962
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
From a maintenance point of view as well, I'd say WebLogic is the better way to go -- I've known BEA to release customized patches on request but I haven't seen IBM do the same.

(Again, the same disclaimer about not having seen much WebSphere around)
 
ss reddy
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Lasse & Paul,

Many many thanks for your prompt reply. You gave me good idea about the best product in terms of developing and maintaining code. But you know marketing strategies of corporate firms like Big Blue so I need answer from you in terms of market share( current and future), number of developers available in market, chances of getting job as developer or administrator for these products, job competition, pay and future market trends. As a software developer you have to take care of these also, what do you say.

Waiting for reply,
ss reddy
SCJP, SCWCD
 
Lasse Koskela
author
Sheriff
Posts: 11962
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The market share as well as the skills market is probably a very close tie between WebLogic and WebSphere. I've seen reports that WebSphere would've bypassed WebLogic from the #1 seat but that might be just IBM changing the way it calculates the usage... Also, WebSphere is much more popular among financial institutions, mostly because of them running IBM's old CICS systems as the legacy their new applications need to integrate with and IBM has managed to convince the decision makers about their advantage in this situation.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic