|
> From: Dieter Bender > > i would not agree with this statement. That's okay. That's what mailing lists are for <grin>. > There are some drawbacks with EJBs, if > you have other applications sitting on the same database, wich can't use > your ejb layer, you might come in some trouble Yeah, that's a BIG problem, Dieter. Among many. > and for small applications the > programmer overhead might be a contra argument. Another huge problem. > But you will get more scalability with ejbs than without and you will get > some benefits for your design. Says who? Why do you think all the overhead of EJB will somehow translate to scalability? In fact, every application designer I've talked to points to EJB overhead as the primary reason their applications DON'T scale. Instead, the only real benefit of EJB is some level of database independence, and that is only if you use CMP. Unfortunately, CMP has a number of design flaws, especially in commitment control, that make it all but unusable in transaction-oriented business applications. And while BMP can be tuned to some level of acceptable performance, you then lose basically all the benefits, however meager, of the EJB design. No, even if you go on the pure Java boards, you'll see that more and more the EJB architecture is being replaced by lightweight ORM engines such as Hibernate. If you continue to use EJB, you do it at your own peril. Joe
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.