Database Management System Architecture

0.0(0)
studied byStudied by 0 people
0.0(0)
full-widthCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/35

encourage image

There's no tags or description

Looks like no tags are added yet.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

36 Terms

1
New cards

DBMS ARCHITECTURE

defines how users interact with the database to read, write, or update information. A well-designed architecture and schema (a blueprint detailing tables, fields and relationships) ensure data consistency, improve performance and keep data secure.

2
New cards
  • 1-Tier Architecture

  • 2-Tier Architecture

  • 3-Tier Architecture

TYPES OF DBMS ARCHITECTURE(3)

3
New cards

1-Tier Architecture

The user works directly with the database on the same system. This means the client, server, and database are all in one application. The user can open the application, interact with the data, and perform tasks without needing a separate server or network connection.

4
New cards
  • Simple Architecture

  • Cost-Effective

  • Easy to Implement

ADVANTAGES OF 1-TIER ARCHITECTURE (3)

5
New cards

Simple Architecture

1-Tier Architecture is the most ______ _________ to set up, as only a single machine is required to maintain it.

6
New cards

Cost-Effective

No additional hardware is required for implementing 1-Tier Architecture

7
New cards

Easy to Implement

1-Tier Architecture can be easily deployed and hence it is mostly used in small projects

8
New cards
  • Limited to Single User

  • Poor Security

  • No Centralized Control

  • Hard to Share Data

DISADVANTAGES OF 1-TIER ARCHITECTURE (4)

9
New cards

Limited to Single User

Only one person can use the application at a time. It’s not designated for multiple users or teamwork

10
New cards

Poor Security

Since everything is on the same machine, if someone gets access to the system, they can access both the data and the application easily.

11
New cards

No Centralized Control

Data is stored locally, so there’s no central database. This makes it hard to manage or back up data across multiple devices

12
New cards

Hard to Share Data

Sharing data between users is difficult because everything is stored on one computer

13
New cards

2-Tier Architecture

similar to a basic client-server model. The application at the client and directly communicates with the database on the server side. APIs like ODBC and JDBC are used for this interaction. The server side is responsible for providing query processing and transaction management functionalities

14
New cards
  • Easy to Access

  • Scalable

  • Low Cost

  • Easy Deployment

  • Simple

ADVANTAGES OF 2-TIER ARCHITECTURE (5)

15
New cards

Easy to Access

2-Tier Architecture makes easy access to the database, which makes fast retrieval

16
New cards

Scalable

We can scale the database easily, by adding clients or upgrading hardware

17
New cards

Low Cost

2-Tier Architecture is cheaper that 3-Tier Architecture and Multi-Tier Architecture

18
New cards

Easy Deployment

2-Tier Architecture is easier to deploy than 3-Tier Archtecture

19
New cards

Simple

2-Tier Architecture is easily understandable as well as simple because of only two components

20
New cards
  • Limited Scalability

  • Security Issues

  • Tight Coupling

  • Difficult Maintenance

DISADVANTAGES OF 2-Tier Architecture (4)

21
New cards

Limited Scalability

As the number of users increase, the system performance can slow down because the server get overloaded with too many requests

22
New cards

Security Issues

Clients connect directly to the database, which can make the system more vulnerable to attacks or data leaks

23
New cards

Tight Coupling

The client and server are closely linked. If the database changes, the client application often needs to be updated too

24
New cards

Difficult Maintenance

Managing updates, fixing bugs, or adding features become harder when the number of users or systems increases

25
New cards

3-Tier Architecture

there is another layer between the client and the server. The client does not directly communicate with the server. Instead, it interacts with an application server which further communicates with the database system and then the query processing and transaction management takes place. This intermediate layer acts as a medium for the exchange of partially processed dat between the server and the client,

26
New cards
  • Enhanced Scalability

  • Data Integrity

  • Security

ADVANTAGES OF 3-Tier Architecture (3)

27
New cards

Enhanced Scalability

Scalability is enhanced due to the distributed deployment of application servers. Now, individual connections need not be made between the client and server

28
New cards

Data Integrity

3-Tier Architecture maintains ____. Since the is a middle layer between the client and the server, data corruption can be avoided/removed

29
New cards

Security

3-Tier Architecture improves ____. This type of model prevents direct interaction of the client with the server thereby reducing access to unauthorized data.

30
New cards
  • More Complex

  • Difficult to Interact

  • Slower Response Time

  • High Cost

DISADVANTAGES OF 3-TIER ARCHITECTURE(4)

31
New cards

More Complex

3-Tier Architecture is more complex in comparison to 2-Tier Architecture. Communication Points are also doubled in 3-Tier Architecture

32
New cards

Difficult to Interact

It becomes difficult for this sort of interaction to take place due to the presence of the middle layers

33
New cards

Slower Response Time

Since the request passes through an extra layer (application server), it may take more time to get a response compared to 2-Tier systems

34
New cards

High Cost

Setting up and maintaining three separate layers (client, server, and database) requires more hardware, software, and skilled people. This makes it more expensive.

35
New cards

SQL (Structured Query Language)

a specialized programming language designed for managing and manipulating data stored in relational database. It is particularly useful for handling structured data, which involves relations among entities and variables.

36
New cards

Supabase

Firebase Alternative

Explore top flashcards

Nisäkkäät
Updated 773d ago
flashcards Flashcards (47)
31-35
Updated 79d ago
flashcards Flashcards (69)
BIOL 375 Exam 2
Updated 1026d ago
flashcards Flashcards (76)
MB3
Updated 191d ago
flashcards Flashcards (37)
Tema 6: Contexto 2
Updated 970d ago
flashcards Flashcards (30)
Emotions and moods
Updated 187d ago
flashcards Flashcards (114)
Nisäkkäät
Updated 773d ago
flashcards Flashcards (47)
31-35
Updated 79d ago
flashcards Flashcards (69)
BIOL 375 Exam 2
Updated 1026d ago
flashcards Flashcards (76)
MB3
Updated 191d ago
flashcards Flashcards (37)
Tema 6: Contexto 2
Updated 970d ago
flashcards Flashcards (30)
Emotions and moods
Updated 187d ago
flashcards Flashcards (114)