Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I found this blog that talks about a certain product i think but same principle holds i believe <a href="http://www.ektron.com/billcavablog/your-questions-answered-3tier-or-2tier/" rel="nofollow">http://www.ektron.com/billcavablog/your-questions-answered-3tier-or-2tier/</a></p> <p>The author has listed five criteria (attributes) to help make the decision:</p> <blockquote> <ul> <li>Security - Some organizations, such as financial institutions, have network policies that state that the forward facing website cannot communicate directly with the database. These organizations require the database to sit on a network that is unreachable from the forward facing website. In cases like this, a 3-tier architecture is a requirement because it satisfies this network policy, since the forward facing front-end website only communicates with the middle-tier and has no knowledge of any database.</li> <li>Scalability - You might be developing a marketing website that needs to be able to handle spikes in seasonal traffic. To satisfy this requirement, you may need to scale out the number of front-end machines available on short notice. Since the front-end has a very minimal Ektron footprint (no Ektron installation, few DLLs, no workarea), scaling horizontally is very simple. For example, using Amazon EC3, you can easily scale horizontally by spining up new machine instances of your front-end.</li> <li>Performance - To minimize the chattiness between the front-end and middle-tier servers in a 3-tier architecture, Ektron provides a caching layer that sits just below the Framework APIs and resides on the front-end. This layer handles the transparent storing, retrieving, and expiring of its data. Technically, this caching layer is also available in 2-tier architecture -- but it's something to keep in mind while working with 3-tier in particular, given its role in minimizing network requests to the middle-tier and improving performance.</li> <li>Availability - If you have particularly high uptime requirements, you might consider 3-tier for its ability to serve cached data from front-end memory, even in cases where the middle-tier or database are unavailable.</li> <li>Interoperability - Using 3 tier opens up the possibility of using any web application framework on the delivery tier, such as ASP.NET Web Forms (Web Application), Web Forms (Web Site), or even ASP.NET MVC. The service layer can also be consumed by any front-end application that can communicate with WCF service layer (Java, etc).</li> </ul> </blockquote>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload