Re: choices in J2EE architecture

["David W" <davdouglas69@hotmail.com>]

all of which will run slower than you want.   there's more to this than the
code.  design patterns plus other algorithms play a huge role.

dw
----- Original Message -----
From: "Johnny Ren" <johnnyren@yahoo.com>
To: "Charles Coombs" <ccoombs@attbi.com>; "ajug-members"
<ajug-members@www.ajug.org>
Sent: Monday, June 16, 2003 9:01 PM
Subject: Re: choices in J2EE architecture


> Select an architecture for Web based applications
>
> There are three popular options.
> Option 1 : JSP/Servelet + JDBC
> Option 2 : JSP/Servlet + Session Bean + JDBC
> Option 3 : JSP/Servlet + Sssion Bean + Entity Bean
>
> Option 1 is a good choice if
>   * Web is the only interface you are going to provide
> to users
>   * there is little transaction requirement
>
> Option 2 is a good choice if
>    * you need provide both ejb and web interfaces to
> your customers.
>    * there is little transaction requirement
>
> Option 3 is a good choice if
>     * you need provide both ejb and web interfaces to
> your customers.
>     *  transaction requirement
>
> There is a lot of discussions regarding these
> architecture at JavaRanch.
>
>
>
> --- Charles Coombs <ccoombs@attbi.com> wrote:
> > I'd like to foment a little discussion regarding
>
>
> =====
> ================================================
> Johnny Ren
> Sun Certified Enterprise Architect
> Sun Certified Web Component Developer
> IBM OOA/OOD with UML, IBM J2EE Connectivity
> Weblogic 6.0 Certified Developer, JCert enterprise developer
>
> __________________________________
> Do you Yahoo!?
> SBC Yahoo! DSL - Now only $29.95 per month!
> http://sbc.yahoo.com
>
>