Hey guys im doing my campus project and i can't seen to figure out how to develope it using the above method.I did it the normal way and everything works fine i just cannot figure out what goes where in 3 tire design.Its a simple program that connects to a database ,adds data and searches for records using stored procedure method.Anyone care to help or provide me with a downloadable tut or anything.This project is due tomorrow.
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: What's the most interesting small town you've visited in South Africa?
3 tire application design
- Thread starter Tejen
- Start date
Tier - It's 3 tier 
Essentially the GUI (program, where the users enter data), goes on the client side.
The BI component, i.e. the part that actually manipulates the data, goes on an application server.
The third tier is the database and hosts the data.
Example: a user at a bank enters client data at a branch for a new loan application (Tier1). The press submit, and the data is sent to an application server which calculates if they qualify for a loan (Tier2). The data is then stored on a database for further manipulation (tier3).
Your Tier2 and Tier3 appear to both be running on a single machine; simply break the logic components (those that manipulate data) from the data storage components (that which stores data) to create Tier2 and 3.
Essentially the GUI (program, where the users enter data), goes on the client side.
The BI component, i.e. the part that actually manipulates the data, goes on an application server.
The third tier is the database and hosts the data.
Example: a user at a bank enters client data at a branch for a new loan application (Tier1). The press submit, and the data is sent to an application server which calculates if they qualify for a loan (Tier2). The data is then stored on a database for further manipulation (tier3).
Your Tier2 and Tier3 appear to both be running on a single machine; simply break the logic components (those that manipulate data) from the data storage components (that which stores data) to create Tier2 and 3.
FarligOpptreden
Executive Member
A good principle in a 3-tier design is to model ALL your data-entities as objects (classes) and only ever reference the classes in your presentation-tier (GUI). Associate all behavior for the entities as methods in the objects and remove any business logic from the presentation-tier.
The initial "design" of the application might take a bit longer to get down, but as soon as the data / business tiers are done, the presentation tier should be a breeze. It also makes maintenance and debugging a LOT easier - almost to the level of MVC.
The initial "design" of the application might take a bit longer to get down, but as soon as the data / business tiers are done, the presentation tier should be a breeze. It also makes maintenance and debugging a LOT easier - almost to the level of MVC.
2cute2shy
Well-Known Member
Hi ,
Depends on the language , you can include web services etc , throw xml etc
Depends on the language , you can include web services etc , throw xml etc
semaphore
Honorary Master
- Joined
- Nov 13, 2007
- Messages
- 18,635
- Reaction score
- 9,721
FarligOpptreden is correct and a good read of the model-view-controller(MVC) pattern will be useful. This follows the OO concept of abstraction where complexity is hidden i.e. a seperation of concerns.
This is taken to the next level where code dealing with data, presentation and the business model are abstracted from each other.
You might want to read up on EE5 frameworks such as JSF (Faces) as well as EJB3.
And its not meant to be TIREsome in the least but on the contrary having tiers within an enterprise application makes code more manageable.
This is taken to the next level where code dealing with data, presentation and the business model are abstracted from each other.
You might want to read up on EE5 frameworks such as JSF (Faces) as well as EJB3.
And its not meant to be TIREsome in the least but on the contrary having tiers within an enterprise application makes code more manageable.
FarligOpptreden
Executive Member
How is that 3 tier?
He's probably trying to insinuate that you can just serialize the objects to XML for passing with SOAP... I dunno?