Granny's Programming Pearls
"inside of every large program is a small program struggling to get out"
JavaRanch.com/granny.jsp
Win a copy of Kotlin in Action this week in the Kotlin forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Advantages of Using EJB  RSS feed

 
Ajit Wadekar
Greenhorn
Posts: 20
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Folks,

I am brand new to the EJb technologiy and would like to know:
What are the advantageous of using EJB over POJO + JDBC
1) Performance
2) Ease of Using
3) Cost
4) Scalable
5) Portability
5) Adding new Logic to the Application

and any other parameters?

Thanks

Ajit
 
Chris Mathews
Ranch Hand
Posts: 2712
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Advantages of EJBs?
1) Performance - EJBs are additional overhead.
2) Ease of Using - Most would argue EJBs are a very complicated beast.
3) Cost - Have you seen how much Websphere and WebLogic cost lately?
4) Scalable - Good software scales, bad software doesn't scale. It doesn't matter what technology you are using.
5) Portability - Can't get more portable than POJOs.
6) Adding new Logic to the Application - See point 2.

Basically, I wouldn't consider any of the points that you listed as benefits of EJBs. If you want to see my complete thoughts on the issue then read the article I wrote for the JavaRanch Journal in Janurary: A Case Against EJB.
[ May 28, 2004: Message edited by: Chris Mathews ]
 
Luigi Smith
Ranch Hand
Posts: 54
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hold on to your hats, EJB 3.0 will save the day: http://radio.weblogs.com/0135826/2004/05/07.html
http://radio.weblogs.com/0135826/2004/05/09.html

Even Hibernate's Gavin King is on the EJB bandwangon now!

Despite the short-comings of the current EJB spec, it is a *standard* for persistence, transactions, messaging, etc. Many company's have invested a lot of resources in this technology, so you should definitely look at the big picture for your organization. Moreover, the tools have come a long way in making RAD tools for EJB, so I don't have to concern myself with writing a lot of SQL (I'm an object expert, not a SQL expert).

Take into consideration where you're going with the technology because I for one think EJB is here to stay. It's just too bad that there's so much in-fighting in the Java community around this topic. Certainly more concerted efforts are required to maintain the advantage over .NET.

My $.02...
 
Chris Mathews
Ranch Hand
Posts: 2712
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Luigi Smith:
Hold on to your hats, EJB 3.0 will save the day

I wouldn't go that far.

In fact, it is safe to say that EJB 3.0 will not solve problems any better than we can today without EJB using products like WebWork, Hibernate, and Spring. The only difference is we will need to shell out $$$ for the privilege of using a top-notch EJB Container. For all practical purposes EJB 3.0 is at least three years out from mainstream adoption so it doesn't do anything for us today anyways. By the time EJB 3.0 is out, other products like JDO, Hibernate, and Spring will be much further along the path. Basically, like any other specification, EJB is be in a constant state of playing catch up.
[ May 30, 2004: Message edited by: Chris Mathews ]
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!