Win a copy of Design for the Mind this week in the Design forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Weaknesses of a 2-tier architecture

 
Eugene Sun
Greenhorn
Posts: 17
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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 ?


Thanks,
Eugene
 
Hu Rui
Greenhorn
Posts: 18
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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


 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic