Data Warehouse Two-tier Architecture in Details

  • Post author:
  • Post last modified:February 26, 2018
  • Post category:Data Warehouse
  • Reading time:3 mins read

Usually, data warehouse adapts either two-tier or three-tier architecture. We have discussed three-tire architecture in my other post ‘Data Warehouse Three-tier Architecture‘. In this article, we will discuss on the data warehouse two-tier architecture.

Data Warehouse Two-tier Architecture 

The data warehouse two-tier architecture is a client – server application. There is a direct communication between client and data source server, we call it as data layer or database layer. Usually, there is no intermediate application between client and database layer.

Below diagram depicts data warehouse two-tier architecture:

Data Warehouse two-tier architecture

As shown in above diagram, application is directly connected to data source layer without any intermediate application.

Example of the two-tier architecture would be storing patient related data into the database and retrieving patient information when required.

Data Warehouse Two-tier Architecture Components

Following are the two-tier architecture components

Client Application – Client tier

Client tier is the front-end application that client uses to get data out from the data warehouse or data tier. On the application tier code is writter for saving data or getting data out of database.

Usually, data warehouse reports are hidden in the GUI to show the required reports.

Database – Data tier

Database or data tier is where the actual data is stored. Various ETL processes are used to load data into database or data warehouse.

Advantages of Data Warehouse Two-tier Architecture

  • Following are the some of the advantages:
  • Easy to maintain
  • Modification of the stored data is easy

Disadvantages of Data Warehouse Two-tier Architecture

  • Following are the some of the disadvantages:
  • Performance will be degraded with increase user traffic
  • Cost – ineffective

Read:

Tags: ,