File System Vs DBMS

File System — Data is stored in one or more files with no enforced logical relationships between them. The application or user must remember and maintain relationships.

For example, if user information is split across many files (usernames, passwords, emails, etc.), the developer must manually coordinate the relationships among those files.

DBMS — Modern DBMS software stores data in tables with well-defined relationships (foreign keys, constraints). The DBMS offers built-in operations for creation, definition, update, deletion, access control, and querying.

For example, one table for users (userID, email, firstName, lastName, passwordHash) and another for purchases that references userID — relationships are enforced and queries are easy.

Data Concurrency

Consider two ATM withdrawals occurring simultaneously. Without concurrency control, both transactions might read the same balance and allow double withdrawal. File systems lack robust locking/concurrency control. Modern DBMS provide built-in concurrency mechanisms (transactions, locks, isolation levels).

Data Searching

DBMS provide efficient, indexed search capabilities and powerful query languages (e.g., SQL). File systems require custom code for complex searches, which is slower and error-prone.

Data Integrity

DBMS enforce data types and constraints (e.g., an integer-only RollNo), ensuring consistent valid data. File systems typically lack such constraints.

Data Sharing

DBMS include access control, roles and permissions to safely share data across applications and users. Implementing secure sharing in plain file systems is complex.

Data Redundancy & Inconsistency

Without relationships, updates in one file may not reflect in another, causing inconsistency. DBMS use normalization and relationships to reduce redundancy and maintain consistency.

Tabular Format

DBMS commonly store data in tables (rows and columns), which is structured for queries and joins. File-based data is often unstructured or semi-structured.