This content has been marked as final.
Show 7 replies
-
1. Re: Struts - to EJB or not - scalability & performance
pharaoh May 8, 2003 7:20 AM (in response to bstil)"Pharaoh" wrote:
"Pharaoh" wrote:
Struts + EJB, or Struts + no EJB..
picking between the two , does not directly effect if one performance and scalibility is better than the other..it depends on who you write the code... depending on the complexity of your project you don't use every patterns they suggest for every project...
Struts was designed to further loosely coupled business logic processign from the client... it was not designed with EJB in mind(though it fits nicely)
Pharaoh. -
2. Re: Struts - to EJB or not - scalability & performance
pharaoh May 8, 2003 7:20 AM (in response to bstil)"Pharaoh" wrote:
"Pharaoh" wrote:
Struts + EJB, or Struts + no EJB..
picking between the two , does not directly effect if one performance and scalibility is better than the other..it depends on who you write the code... depending on the complexity of your project you don't use every patterns they suggest for every project...
Struts was designed to further loosely coupled business logic processign from the client... it was not designed with EJB in mind(though it fits nicely)
Pharaoh. -
3. Re: Struts - to EJB or not - scalability & performance
petermd May 22, 2003 6:32 AM (in response to bstil)"petermd" wrote:
"petermd" wrote:
imho you should only use ejbs if you really require the extra services they provide, i.e. transactions, remote-access, security. there is always an overhead (performance, complexity, implementation) in using them, so it must be worth it.
if your application has some of the following attributes
- is a web app
- most actions will be reading the database not writing
- queries across objects / tables
- is high-volume
- shares the database with other applications
then you probably don't need/can't use the services ejbs provides.
as a general design rule. i would still use a facade or delegate pattern to seperate the struts tier from the business tier, and the dao/vo pattern for data access. which would allow you to introduce session ejbs/bmps into the design at a later stage if required. -
4. Re: Struts - to EJB or not - scalability & performance
petermd May 22, 2003 6:33 AM (in response to bstil)"petermd" wrote:
"petermd" wrote:
imho you should only use ejbs if you really require the extra services they provide, i.e. transactions, remote-access, security. there is always an overhead (performance, complexity, implementation) in using them, so it must be worth it.
if your application has some of the following attributes
- is a web app
- most actions will be reading the database not writing
- queries across objects / tables
- is high-volume
- shares the database with other applications
then you probably don't need/can't use the services ejbs provides.
as a general design rule. i would still use a facade or delegate pattern to seperate the struts tier from the business tier, and the dao/vo pattern for data access. which would allow you to introduce session ejbs/bmps into the design at a later stage if required. -
5. Re: Struts - to EJB or not - scalability & performance
darryl_staflund Aug 5, 2003 11:01 AM (in response to bstil)"darryl_staflund" wrote:
"darryl_staflund" wrote:
Hi there,
I was lucky enough to build a Struts/EJB application following Wrox's recommendations and the application runs well. The more important issue (IMHO) that needs to be considered before you starting coding such an application, however, is whether you will using BMP or CMP, and if the latter, whether CMR will be used as well. Whether or not you use these technologies will have great impact on whether and how you choose to implement DOs and VOs and, if so, how the responsibility will be distributed for making them. This is even more important if the presentation and business tiers reside on different nodes since the business delegate AND certain objects in the business tier will all need to be able to create VOs at one time or another.
Darryl -
6. Re: VOs still needed
trajano Dec 7, 2003 8:43 PM (in response to bstil)"trajano" wrote:
"trajano" wrote:
Are VO's still needed when using local references?
Assuming (VO == value object) -
7. Re: Struts - to EJB or not - scalability & performance
apdo Feb 5, 2004 12:57 AM (in response to bstil)VO is still needed when business tier send data to the presentation tier.