Application Architecture Design Question

Question

0.00/5 (No votes)

See more:

Hello Architects/Experts,

I need your suggestions in designing a Java/J2EE web based application. Here are its characteristics:

1. Purely database oriented application (with 10 tables). The database is Oracle.
2. Three different types of interfaces/screens:
2.1 WebSphere Portlets (6 Interfaces/Screens)
2.2 Handheld Device (5 Interfaces/Screens)
2.3 Web Application (17 Interfaces/Screens)
3. Few of the screens are just report which will be built using Crystal Reports.
4. There isn't much business logic involved.

Now my concerns are:

1. Which architecture should I go for 2 tier or 3 tier?
2. Which frameworks should I use struts/jsf (MVC)? If any? Or should I go for simple POJO based programming without any framework.
3. The biggest concern is packaging, I mean I don't want to replicate the business and database layer for each three different types of interfaces I want to develop. Do you think EJB will be good option to expose DB/Business layer? How should I handle this?
4. Should I use any specific framework like sitemash for presentation layer?
5. Should I use any specific framework for database layer JPA/Hibernate or should I use simple JDBC?

Any comments/suggestions are welcome...

BR
SC

Posted 17-Dec-10 9:17am

SmoothCriminel

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Wild-Programmer · Answer 1 · 2010-12-17T18:49:00

While designing the architecture always keep in mind Cohesion and coupling. Higher be the cohesion and lower the coupling. The dependency between the UI and access layer(s) should be minimal.
Remember, 3 tier and 3 layer are two different things. 3tier is physical separation of layers that are deployed on different servers, whereas 3 layer are logical separation of project (UI, DAL, and BAL).

As per your details, you have trivial business logic, you can go for 2 layered architecture. In can you have 2 separate server, go for 2 tier architecture.

MVC is definitely a great concept of separating UI from its Model but is little complex to code. Plan an design method that will be easier for maintenance.

Rest Java developers will tell you as I am a .NET developer :)