Lesson 2: Understanding Database Systems and Their Types

0.0(0)
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
Card Sorting

1/46

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.

47 Terms

1
New cards

Single-user database

Supports only one user at a time; a single-user database that runs on a personal computer is called a desktop database.

2
New cards

Multiuser database

Supports multiple users at the same time.

3
New cards

Workgroup database

A multiuser database that supports a relatively small number of users (usually fewer than 50) or a specific department within an organization.

4
New cards

Enterprise database

Used by the entire organization and supports many users (more than 50, usually hundreds) across many departments.

5
New cards

Centralized database

A database that supports data located at a single site.

6
New cards

Client/server architecture

Systems that use one or more client nodes directly connected to a central server.

7
New cards

Global clock

A clock of the central node that all client nodes sync up with.

8
New cards

Central node

One single central unit which serves/coordinates all the other nodes in the system.

9
New cards

Dependent failure of components

Central node failure causes the entire system to fail.

10
New cards

Components of Centralized System

Includes Node (Computer, Mobile, etc.), Server, and Communication link (Cables, Wi-Fi, etc.).

11
New cards

Client-Server architecture

The central node that serves the other nodes in the system is the server node and all the other nodes are the client nodes.

12
New cards

Centralized System

Single server node manages all data and requests.

13
New cards

Decentralized Database

Each node independently decides, aggregating overall behavior.

14
New cards

Hot Updates

Updates applied without taking the server offline.

15
New cards

Vertical Scaling

Adding resources to a single node for performance.

16
New cards

Peer-to-Peer Architecture

All nodes are equal, with no central authority.

17
New cards

Master-Slave Architecture

One node coordinates others without supreme control.

18
New cards

High Availability

Multiple nodes ensure continuous system operation.

19
New cards

Performance Bottlenecks

Reduced by distributing load across multiple nodes.

20
New cards

Concurrency of Components

Nodes reach consensus on transactions and commands.

21
New cards

Independent Failure

Nodes fail without affecting overall system functionality.

22
New cards

Distributed Database

Data stored across multiple sites for redundancy.

23
New cards

Google Search System

Multiple computers collaborate to return search results.

24
New cards

Cluster Computing

Multiple computers work together as a single entity.

25
New cards

Grid Computing

Pooling resources to create a powerful supercomputer.

26
New cards

Organisations Using Centralized Systems

National Informatics Center, IBM.

27
New cards

Organisations Using Decentralized Systems

Bitcoin, Tor network.

28
New cards

Data Analysis

Simplified when data is centralized.

29
New cards

Operational Database

Supports daily operations; also called transactional database.

30
New cards

Data Warehouse

Stores data for tactical and strategic decision-making.

31
New cards

Data Massaging

Data manipulation to extract useful information.

32
New cards

Unstructured Data

Data in original raw format, not organized.

33
New cards

Structured Data

Formatted data for storage and information generation.

34
New cards

Semistructured Data

Processed data presented in a prearranged format.

35
New cards

XML (Extensible Markup Language)

Language for representing and manipulating data elements.

36
New cards

Database Design

Activities focused on structuring a database.

37
New cards

Manual File Systems

Paper-based systems organized for data use.

38
New cards

Computerized File Systems

Digital files requiring programming for data retrieval.

39
New cards

Data

Raw facts with little meaning until organized.

40
New cards

Field

Character group with specific meaning in data.

41
New cards

Record

Set of fields describing a person, place, or thing.

42
New cards

File

Collection of related records.

43
New cards

ACID Properties

Ensures reliable database transactions.

44
New cards

Atomicity

All operations in a transaction must succeed.

45
New cards

Consistency

Database rules maintain stability before and after transactions.

46
New cards

Isolation

Transactions operate independently without interference.

47
New cards

Durability

Changes persist after transaction completion.