GLOSSARY ENTRY (DERIVED FROM QUESTION BELOW) | ||||||
---|---|---|---|---|---|---|
|
09:32 Apr 7, 2013 |
English language (monolingual) [PRO] Bus/Financial - Insurance / experts | |||||||
---|---|---|---|---|---|---|---|
|
| ||||||
| Selected response from: Charles Davis Spain Local time: 03:00 | ||||||
Grading comment
|
SUMMARY OF ALL EXPLANATIONS PROVIDED | ||||
---|---|---|---|---|
4 +2 | the technology used to run the middle tier in three-tier architecture |
| ||
4 | middle rather than high end technology |
|
the technology used to run the middle tier in three-tier architecture Explanation: This is a computing rather than an insurance term. "Middle layer" refers to a three-tier architecture, in which, in addition to the client tier (user interface) and the database tier (DBMS server) there is an intermediate application server tier. This is necessary when there are a large number of on-line users, in a large enterprise, because in those circumstances problems arise with a two-tier architecture. Performance deteriorates, for various reasons, when a large number of clients are connecting directly to the DBMS server. So a middle tier is introduced to handle the connections. "TIA has a 3-tier, Service Oriented Architecture separating Client Tier from Application Server Tier from Database Tier. The Client Tier supports multiple front ends types for the Intranet, Extranet, and Internet, all leveraging the same business logic thereby securing instant access to data from all channels. The Application Server Tier processes requests to the business logic. Common java API’s secure openness and connectivity and supports multiple technologies, e.g., java, .net, etc. The insurer decides on middle layer technology. The Database Tier contains data and business logic to secure highest performance across any channel with minimal network traffic." http://tiatakaful.com/home/?page_id=173 "The industry's response to limitations in the 2-tier architecture has been to add a third, middle tier, between the input/output device (PC on your desktop) and the DBMS server. This middle layer can perform a number of different functions - queuing, application execution, database staging and so forth. The use of client/server technology with such a middle layer has been shown to offer considerably more performance and flexibility than a 2-tier approach. Just to illustrate one advantage of a middle layer, if that middle tier can provide queuing, the synchronous process of the 2-tier approach becomes asynchronous. In other words, the client can deliver its request to the middle layer, disengage and be assured that a proper response will be forthcoming at a later time. In addition, the middle layer adds scheduling and prioritization for the work in process. The use of an architecture with such a middle layer is called "3-tier" or "multi-tier". These two terms are largely synonymous in this context." http://www.dciexpo.com/geos/dbsejava.htm |
| ||||||||||
15 mins confidence:
Login or register (free and only takes a few minutes) to participate in this question. You will also have access to many other tools and opportunities designed for those who have language-related jobs (or are passionate about them). Participation is free and the site has a strict confidentiality policy. KudoZ™ translation helpThe KudoZ network provides a framework for translators and others to assist each other with translations or explanations of terms and short phrases.
See also: Search millions of term translations Your current localization setting
English
Select a language Close search
|