The two-tier application programming model was developed to enhance the file server application programming model. As compared with the file server application programming model, the two-tier application programming model provides you with improved usability, scalability, and flexibility of applications.
In Two-Tier model, you will have two seperate layers namely Client & Server.
The applications developed using the two-tier application
programming model have a user-friendly interface.
These applications can support only a few users and
allow data to be shared within a homogeneous environment.
Example of the Model
The various tiers in a two-tier architecture are separated from each other by physical boundaries. These physical boundaries can be machine boundaries, process boundaries, or corporate boundaries. |
Characteristics 1
Two-tier application programming model is a combination of a client application and a server application. In this application programming model, the client application directly interacts with the server application without the presence of any intermediate application. |
Characteristics 2
Business Logic is coupled either with Client or the Server.
Business Logic In Server
If the Business Logic is coupled with the Client, its called Fat Server with Thin Client.
Business Login In Client
If the Business Logic is coupled with the Server, its called Fat Client with Thin Server.
Characteristics 3
The Client application communicates with the data layer through a database bridge Application Programming Interface (API).
An Example of a database bridge API is JDBC commonly known as Java Database Connectivity.
Characteristics 4
The Database driver is installed in each computer that runs the client application.
If the database changes, we need to reinstall Database driver in all the computer.
This increases Deployment cost
Characteristics 5
Fat Client is bound to a database bridge API, such as relational database API or object database API.
Disadvantage
If you change the type of database used by your organization, you need to redeploy and reconfigure each client application
Characteristics 6
Each client establishes a separate database connection.
Database connections are limited in number and are expensive to establish.
Disadvantage:
Database Connection is retained even when the client is not accessing the database.
This makes the database connection unavailable to other users.
Therefore Only a limited number of clients can access the database at a time.
Characteristics 7
High network traffic because of an increase in the number of trips of data transfer across the physical boundaries of the network. Each time a database operation is performed, the data is transmitted across the physical boundary that separates the business logic and data layers
Usage:
Suitable for environments where business rules do not change frequently and the number of users are limited.
For E.g.: This model can be used to run the localized accounting application of a company.
Nice to see an Indian blog in top 3 blogs of wordpress 🙂
All the best:)
if time permits visit: aravinthan.wordpress.com
Good pictures and summary. Could have been a bit more better if you had explained it a little more.
I thought most of the pictures..are self explanatory..
any way..whenever i find time i will update with explanations.
hey its good., picture speaks more than words. …
self explanatory
Nice Images But it could be Briefly Explained
Visual effect is obviously far more than reading. But still feel that more explanation would decor this article
i want info about fatserver
tttttttthanks preparin notes for ma sessionals thanks for the share
Very nice,no words to express
it’s really good explanation with pictures thanks for the share a good think.
Hi,
In the article given abvove, under the characteristic 2 there is a statement written which says that “If the Business Logic is coupled with the Client, its called Fat Server with Thin Client”.
However, the supporting diagram shown for this article shows that “The Business Logic is coupled with the Server (Not with the client), and its been denoted as Fat Server with Thin Client”.
Ideally the correct definition of fat client/server is as follows
1. “If the Business Logic is coupled with the Client, its called Fat Client with Thin Server”.
2. “If the Business Logic is coupled with the Server, its called Fat Server with Thin Client”.
This is fantastic overview.
in reality your information is very useful and utilisable. but for me too huge and many data’s for comprehensing(understood). so it is little bit ambigious. so i kindly request you to explaine me a sweet and short of single ,two and multi tier architecture.
merci
Ibrahim
This is fantastic overview.
picture speaks more than words. …
Thanks, fantastic explanation. very useful diagram.
Thanks lot…..
Ramakrishnan S
Nice Work .., It’s great to see tamilian work in net. Appriciated and keep going.u can do more
Hi
Nice content.
You have explained the concept very clearly , Use of graphical images is awesome.
But try to give more examples. Example portion is missing.
nice…….it’s very nice.
u had provide good info.
Hi Bhuvan,
Can you give me some names of Companies that have excelled in implementing the two tiered architecture model??
Very nice
now-days which company is usind the two-tier architecture
Its really helpful…
hey…its nice..
i like it…
very nice realy no words to express how beautifully, writer has explained this topic
It is very nice. Appreciable and great work.
nice one….do u knw any dotnet related blogs?
well
good one, and very nice.
very well
thanks really it develop great understanding…………
good one. no need of word to xplain it. bhuvana rocks.
nice one..so many diagrams n it explains the process…nice…
very good explaination
Many thanks for this clssified exlaination. No more retakes in client server.
Really Thanks For This Two Tier Architecture
thnx….bro…reaallly gonna help for my xam…2mrw…thnx..:)
Good Explanation. cheer up!
Thanks for the explanation. Very well…
Thanks. I know about j2ee architectures and more info
Good explanation!!!!!
really enjoyed reading the blog. bhuvans, you have great writing skills..
This is very interesting and nice to read, I like the interesting article … good luck salam sukses..
awsome explanation!! was able to make quick grasp!!
really enjoyed reading the blog. bhuvans, you have great writing skills..
Gunakan waktumu dengan bijak dan jangan sia-siakan meskipun hanya satu menit.
Hal lain yang bisa menjadi penyebab penularan dalah dengan menggunakan peralatan yang sama dengan penderita seperti handuk dan benda lainya.
Jangan habiskan waktumu memimpikan sesuatu yang tidak mungkin terjadi ketika kamu bisa bangun dan membuat sesuatu terjadi.
Dreaming is the first step that you have to make While the act is the next step that you have to do
I found a correction in characterstic 2. I hope you will correct it.