Win a copy of The Business Blockchain this week in the Cloud forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Architecture for a small size web application

 
subba Sathi
Greenhorn
Posts: 8
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I would like to develop a small size web app(3-5 screens) that needs to access DB2 table in the backend..

What should be the technology used..

JSP/Servlets/java beans
Here how does the database connection happens
What is the architecture diagram look like? like presentation layer/business logic layer/data access layer etc..


JSP/Servlets/EJB - Does it need EJB for a small size app..


Please advise..

PS. I would like to know different combinations of architecture designs for various types of web applications like small, medium and large applications..

can someone guide me thru this.. i am being exposed to web technologies recently and would know JSP/Servlets only..

Presentation Layer - JSP/Servlets
Business Logic Layer - Java Beans
Data Access layer - JDBC


ThankS
Subba S

[ July 02, 2008: Message edited by: subba Sathi ]
[ July 02, 2008: Message edited by: subba Sathi ]
 
Benoît de Chateauvieux
Ranch Hand
Posts: 183
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Subba,

For me, the faster and simpler way to achieve this kind of apps is:
Presentation Layer - JSF
Business Logic Layer - EJB3
Data Access layer - EJB3/JPA

You'll have access to great frameworks (JSF, EJB) that will reduce your development time, letting you focus on your the Business of your application instead of re-inventing a Controller, managing JDBC connections, etc.

Hope it helps,

Beno�t
 
Ayub ali khan
Ranch Hand
Posts: 395
2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Subba,

Have a look at Adventure Builder Demo this has good description on the architecture aspects of an application.

--Ayub
 
Juan Pablo Crossley
Ranch Hand
Posts: 128
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi subba, there're several ways to design your application, so first you need to ask you for some of these:

1. How many users will use your application (at the same time).
2. Will you require cluster (fail/over support)?
3. Do you have access to a server application? (many customers don't have a stuff in their team to admin the J2EE servers properly)
4. How big is your application? (the screens are not a good measure, you can have 2 screens... google has it... and process a huge logic from behind)
5. What about the security level? will be a sensitive information application? (banking? customer information?)

etc.

But keep in mind, you should follow the best design principle of all (K.I.S.S.) keep it simple st. if you don't need Stateless, EJBs, etc, you should go to the easier configuration of all: JSP (JSF is a good MVC), DAO for your persistence, and that's it. If you need a powerful application, with scalable options, and so on... use some combinations of JSF, Sessionbean Stateless and DAOs (yes... without entities). But, if you need cluster, replication, security, etc. etc. etc.... then go for the hard one (in terms of robustness) JSF - Sessionbean - JPA.

You should keep this in mind when you answer the SCEA certification test.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic