I can see why you would think EJB 2 is obsolete or at the very least, taboo after reading this article. Keep in mind the author also wrote a book that he needs to sell, so he is a strong advocate of the POJO approach. Given that, I'm not surprised he never mentioned anything about performance and that a JDBC approach will ALWAYS perform better than an object-relational mapping (persistence) approach. So, if you have a high volume application and like your job, you might want to seriously consider the performance aspect of the argument. The extra coding effort required is usally worth it, and not that much extra to begin with. Otherwise, be prepared to tell your boss how great and "OO" your code is as he boots you out the door for writing an application that can't handle any kind of load in the real world.
|
Previous
Index
Next
Flat
Re: J2EE design decisions
Edit
Reply
Quote
