There has been, over the last year or two, a major push away from using EJBs. In fact the last two companies I have worked for has allowed
EJB development only when absolutely needed (e.g. remote reusable objects). I went to the "No Fluff, Just Stuff" software conference last year and was amazed at the negativity directed at using EJBs. Not just from the attendees but also from the lecturers. For a while, I just thought Bruce Tate was trying to spread a virus or promote his 'Bitter EJB' book but fact of the matter is, the general theme of the conference seemed to be that 'anything you can do with EJBs you can do without them as well'.
Question is, from a scalability and performance standpoint, at what point does
JDBC become insufficient? Honestly, I have never seen a case where JDBC has not done the job. Also, if I come to a point where JDBC becomes unmanageable, unscalable, unacceptable, or whatever, should I use EJBs or JDO? What are the benefits of using one over the other?