> I'm trying t9o make some architecture choices and I'd appreciate any > experience that might help me better understand the likely performance vis-a-vis > three approaches:
I can offer my opinions... > 1. Using EJBs with local itnerfaces. I especially have in mind stateless > session beans unless you have reason to use remote calls, dont - RMI is not cheap in terms of performance. > 2. EJBs calling not EJBs with local interaces but plain old local Java > objects. I can see making the object a servlet calls an EJB, but must > everything be an EJB? I don't think so. If something doesn't need to be an EJB, then dont make it one. The reasons you might want to make something an EJB would include wanting to use the declaritive security/tx management that EJB provides. > 3. Using messaging to communicate with beans and other objects, rather than > using synchronous calls with local interfaces. Thats what MDBs are for. Having a MDB unwrap a message and call a SLSB through a local interface is (IMHO) a perfectly valid way of exposing the same functionality (in a slsb) through a synchronous interface and an asynchronous interface. cheers dim =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
