Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

client/server design - a must?

 
Tobias Nettels
Greenhorn
Posts: 8
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I just read my instructions (B&S) again an see the following passus:
The main architecture of the application must be a traditional client-server system. There are three key parts: the server-side data management system, the client-side GUI, and the network connection between the two.
Does this mean, a 3-tier-solution leads to an automatically failure? I'm actually ready with a 3-tier-solution!
What do you think about this. Does anybody have the same restrictions?
I'm a little bit disturbed...
 
Vishwa Kumba
Ranch Hand
Posts: 1066
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I also have the same instructions. BS 2.1.2
I think what SUN means is that the application is supposed to be a typical client-server application using RMI. 2 pieces of program communicating with each other fulfilling the business functionality.
Whether we expose the methods published in the Sun's DB/DBMain interface to the client is entirely upto us. I am also using a 3-tier solution which I thinkis going to be simpler for me than a 2-tier solution.There have been great debates in the past, but a 3-tier solution is purely my personal choice and both solutions are accepted by SUN. So do not worry.
[ May 06, 2004: Message edited by: Vishwa Kumba ]
 
Philippe Maquet
Bartender
Posts: 1872
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Tobias,
I just confirm what Vishwa wrote. Analysis of past scores prove that both designs (business layer residing server-side or client-side) are equally accepted by SUN.
BTW, does "traditional" mean "old-fashioned"?
Regards,
Phil.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic