File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Architect Certification (SCEA/OCMJEA) and the fly likes Weaknesses of a 2-tier architecture Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Certification » Architect Certification (SCEA/OCMJEA)
Bookmark "Weaknesses of a 2-tier architecture" Watch "Weaknesses of a 2-tier architecture" New topic

Weaknesses of a 2-tier architecture

Eugene Sun

Joined: Aug 09, 2003
Posts: 17
One of the INESystems mock exams says

A 2-tier architecture has the following weaknesses

1) scalability
2) extensibility
3) manageability

I am thinking is manageability really a bigger problem than maintainablity ? I know 2-tier architecture is definitely less manageable than 1-tier one, but I would think maintaining coupled layers in 2-tier architecture should outweigh its manageability issue. Comments ?

Hu Rui

Joined: Nov 19, 2004
Posts: 18
The certification assignment want you to use 3 tie.

How you do your work in practice is another question.

In real world application, you might now use EJB at all. The functionality of EJB can be replaced by plain Java class. So you have almost 2 tie architecture.

In UML design level, EJB = static methods.

2 tie / 3 tie there is no clear line in between.

I like use class then EJB, since if you only use Java code, IDE has wonderful tools like refactoring.

I always wonder how the hell to refactoring an EJB

I agree. Here's the link:
subject: Weaknesses of a 2-tier architecture
It's not a secret anymore!