As can be seen from the above image, the user sends a request through the presentation layer which then sends the request to the business layer. The business layer then processes the request by adding business rules , data rules, business processes and so on, and sends the enriched request to the data access layer.
The data access layer accesses the database for the response and sends it back to the business layer which in turn sends the response back to the presentation layer, which displays the information to the user on a user interface UI. All three tiers in three-tier architecture can be independent of one another in terms of technology, language, logic and platform, and yet need to constantly interact with each other in order to enable the software applications' work.
Since the tiers are independent of each other, their operation, maintenance and troubleshooting are also independent.
It is important that the tiers are both backward and forward compatible with all the components of all other tiers. This tier is responsible for accepting inputs or requests from the user and displaying data for the user in a user-friendly format.
It accepts inputs and sends the inputs or request to the business logic layer. The presentation tier is used when the user provides inputs through one or more channels such as traditional applications, websites , portals , mobile device websites and apps. In three-tier architecture, the presentation layer is a thin client. This tier helps define solutions to complex business problems. The solutions or rules can be defined on a number of components that reside inside the tier.
Software developers can define complex business algorithms , business processes, government or legal rules or data rules that help keep the data structure consistent with one or more databases. These middle-tier components are not tied to any client and can be used by all applications and moved to all places. This tier interacts with persistent data stored in the database or any permanent storage by constructing SQL queries and executing these queries with the help of relevant APIs.
A case study on how three-tier architecture solved real-time business problems is provided below. Global e-commerce giant eBay wanted to improve its profitability and customer satisfaction by improving the reliability of its website to provide real-time marketplace services all over the world and boost customer satisfaction. To find and implement a solution, eBay chose IBM. As a result, eBay developers have a common tool which enables collaboration and sharing of all common Java objects and they can add new website features easily.
This has also contributed to improvement of website reliability and customer experience. While three-tier architecture is almost considered the norm now, for many companies — especially those with limited resources — it is not easy to implement three-tier architecture.
It is a complex system and requires big investment in terms of technology, money and skilled personnel. Does that mean that companies with smaller budgets will not be able to achieve efficiency?
They can, in their own ways. Thanks a lot for sharing the details. Nice post,provide more information of the both architecture Reply. Nice explanation….. Thanks a lot….. Really nice post,got a clear idea about both architecture now.
Thank You…keep going. Simply made to know. Tnks Reply. Very easy to understand. Thank You. Thank You Reply. Thank you for the information. I am a student and this is new to me.
Thanks for your help. Very refreshing and knowledgeable for anyone. Thanks Shammi Reply. Thanks for sharing article, Its simple to understand. So nice presentation of facts.. It made my concept crystal clear.
Very good for beginers Reply. Good for Freshers… Reply. Its soo simple nd easy to understand.. Thank you!! It is good to understand Reply. Crisp, clear, easy to understand explanation of the topic.
It is very nice and useful. Thank you very much Reply. Nice explanation, concept is clear Thank You Reply. Very nice easy to understand lovely.. Usefulll Reply. Thank you Reply. Super Reply. Its a perfect answer for the beginners.. Thank u Reply. Nice and easy to understand Reply. Share This Post. Share on facebook. Share on linkedin. Share on twitter. It helps developers to create flexible and reusable applications.
A diagrammatic representation of an n-tier system depicts here — presentation, application, and database layers. N Tier Architecture Diagram. These three layers can be further subdivided into different sub-layers depending on the requirements.
While Server , on the other hand, is a set of another program, which sends the result sets to the client system as requested. By looking at the below diagram, you can easily identify that 3-tier architecture has three different layers. Here we have taken a simple example of student form to understand all these three layers.
It has information about a student like — Name, Address, Email, and Picture. This is the function of the business layer which accepts the data from the application layer and passes it to the data layer. The code is using the function of business layer, which will accept the data for the application layer and passed it to the data layer. The Business layer codes act as a mediator between the functions defined in the presentation layer and data layer and calling the functions vice -versa.
This is the data layer function, which receives the data from the business layer and performs the necessary operation into the database. The code defines in dataset layer above accepts the entire request: requested by the system and performing the required operations into the database.
0コメント