3-tier vs. 2-tier architecture

[Former Member]

Dear Xperts,

I would like to know your opinion about a 3-tier vs 2-tier BW system architecture.

Why should you choose for 3 instead of 2, or the other way around. Thus pro's & cons.

Thx.

regards,

JvB

[Former Member · Accepted solution]

Hi JvB,

Two-tier architecture is a client/server architecture , where a request to do some task is sent to the server and the server responds by performing the task.where as a three-tier or a multi tier architecture has client, server and database. Where the client request is sent to the server and the server in turn sends the request to the database. The database sends back the information/data required to the server which inturn sends it to the client.

hope this helps you .

If u think it helps , assign points.

regards

santosh

[Former Member]

a. 2 tier application: Clients and data base on different machines. Clinets are thick clients i.e. processing is done at client side. Application layer is on Clients.

b. 3 tier application:Clients are partially thick. Apart from that there are two more layers application layer and database layer.

The difference between 2 tier and 3 tier are as follows:

1.In 2 tier there are only client and server at the other side in 3 tier there are client,server and middle tier.

2. It's not good enough that your end-to-end performance be good, it's also important that those machines service requests quickly, which is where a two-tiered architecture fails (and which is why people came up with the idea of a three-tiered architecture in the first place).This is the difference between performance and scalability.

The other difference between 2 tier and 3 tier are as follows:

1) In a modern two-tier architecture, the server holds both the application and the data. The application resides on the server rather than the client, probably because the server will have more processing power and disk space than the PC.

2) In a three-tier architecture, the data and applications are split onto seperate servers, with the server-side distributed between a database server and an application server. The client is a front end, simply requesting and displaying data.Reason being that each server will be dedicated to processing either data or application requests, hence a more manageable system and less contention for resources will occur.

Thanks & regards,

Shalini

[mlaupiatek]

Hello!

I have a question about implementation of SAP ENABLE NOW,

Which of the two architectures are possible in Sap enable now manager (hana on premise) ?

Application server (Tomcat) and file storage on one machine; HANA database on a second

or

Application server (Tomcat) and HANA database on one machine; file server storage on a second Answer

Thanks!!