Abulag, Lovely T. Bsit Iii-B
Abulag, Lovely T. Bsit Iii-B
Abulag, Lovely T. Bsit Iii-B
BSIT III-B
2. DATABASE ARCHITECTURE
Database architecture uses programming languages to design a particular type
of software for businesses or organizations. Database architecture focuses on the design,
development, implementation and maintenance of computer programs that store and
organize information for businesses, agencies and institutions. A database architect
develops and implements software to meet the needs of users.
1. 1-tier architecture
2. 2-tier architecture
3. 3-tier architecture
4. n-tier architecture
1. 1-tier architecture
One-tier architecture involves putting all of the required components for a software
application or technology on a single server or platform. Basically, a one-tier architecture
keeps all of the elements of an application, including the interface, Middleware and back-
end data, in one place. Developers see these types of systems as the simplest and most
direct way.
2. 2-tier architecture
The two-tier is based on Client Server architecture. The two-tier architecture is like client
server application. The direct communication takes place between client and server.
There is no intermediate between client and server.
3. 3-tier architecture
A 3-tier architecture separates its tiers from each other based on the complexity of the
users and how they use the data present in the database. It is the most widely used
architecture to design a DBMS.
This architecture has different usages with different applications. It can be used in web
applications and distributed applications. The strength in particular is when using this
architecture over distributed systems.
1. Database (Data) Tier – At this tier, the database resides along with its query
processing languages. We also have the relations that define the data and their
constraints at this level.
2. Application (Middle) Tier – At this tier reside the application server and the
programs that access the database. For a user, this application tier presents an
abstracted view of the database. End-users are unaware of any existence of the
database beyond the application. At the other end, the database tier is not aware of
any other user beyond the application tier. Hence, the application layer sits in the
middle and acts as a mediator between the end-user and the database.
3. User (Presentation) Tier – End-users operate on this tier and they know nothing
about any existence of the database beyond this layer. At this layer, multiple
views of the database can be provided by the application. All views are generated
by applications that reside in the application tier.
4. n-tier architecture
N-tier architecture would involve dividing an application into three different tiers. These
would be the logic tier, the presentation tier, and the data tier.