For Programmers: Free Programming Magazines  


Home > Archive > Java Beans > December 2004 > EBJ horror stories









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author EBJ horror stories
eJAYBee

2004-12-13, 9:00 pm

Could you J2EE gurus share your EJB horror stories? Touching upon
issues like scalability, migration, vendor lock-in, etc. I am
architecting a system that needs to support 110 TPS. Need to stay away
from pit falls. Any suggestions and pointers will be a great help.

Robert kebernet Cooper

2004-12-14, 3:57 am

I can tell you my first experiences with EJBs several years ago was
profoundly negative. Most of this, however, was a result of a lack of
experience on my part as well as a lesser maturity among tools and
servers.

We made all the classic mistakes: too fine grained EJBs, session beans
were too weak, too much over the wire, etc. Frankly, I have now moved
almost completely away from EJBs in a lot of respects now in favor of
SOA and EJB-as-SOAP-Service and other persistence systems, though the
3.0 spec has me very very excited.

There are a lot of good materials out there now on best practices with
J2EE stuff. Which ones you choose is really more about the project you
are working on though.

Sponsored Links







Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive

Copyright 2008 codecomments.com