DBMS Architecture & Models || DBMS Tier Architecture

-

DBMS Architecture & Models

  1. DBMS Architecture 
  2. DBMS Models
  3. Data Independence 
  4. Schema 
  5. Instance 

DBMS Architecture

DBMS Architecture Describe How The Database System Is Structured The Layers, Components And How Users Interact With The Database.

Types Of DBMS Architecture 

  1.  Tier Architecture (Single tier)
  2.  Tier Architecture (Client Server)
  3.  Tier Architecture (Most Common)
Tier Architecture (Single Tier)
  • The User Directly Intercaste With The Database 
  • Not Intermediate Layer (User In Development & Testing)
  • Example: MS Access, Local SQLite 
Tier Architecture (Client Server)
  • Application (Client) Communication Directly With The DBMS (Server)
  • Good For Small To Medium Application 
  • Example: MySQL With Desktop Client Software 




Comments

Post a Comment

Popular posts from this blog

Database Design And ER Diagram || Entity And Attributes

-
Image
Database Design And ER Diagrams What Is ER Model Entities And Attributes  Relationship (1:1 , 1:N , 1:M) Converting ER Diagrams To Tables ∆   ER Diagrams In DBMS (Entity Relationship Diagram) An ER Diagrams (Entity Relationship Diagram) Is A Graphical Representation Of Entities And Their relationship In A Database Design Phase To Visually Map Out How Data Is Connected And Structured • Key Components OF ER Diagram  Entity :- An object Or Thing In the Real World That has Data Stored about it  Attributes :- properties or Details Of An Entity  Relationship :- Shows How Entities Are Related To Each Other  ∆ What Is An Entity   An Entity Is real-world Object Or Concept That Can Be Identified Distinctly And About Which Data Can Be Start In A Database  • Key Point  Entity Represents A Thing Or Object  Each Entity Is Described Using Attributes. Used to Design Tables In A Database  ∆ Type Of Entities  1.  Strong Entity  Ha...
Read more

NoSQL Database || Use NoSQL Database || Hierarchical Database

-
Image
• Structure :- Non- Relation Includes Various Models • Subtypes Document-based :- JSON-Like Documents (eg., MongoDb,CauchDB) Key Value stores :- Simple Key-Value pairs (eg.,Redis DynomoDB) Colum-based :- Colum-Format (eg., Cassandra,HBase) Graph-based :- Notes And Edges For Relationship (e.g., Neo4) • Strengths:- Schema Flexibility  Scalability (especially horizontal) Better for unstructured semi-Structured Data  • Use Cases:- Real Time Analytics,IOT, Social, Networék , Big Data Alls •Where We Use NOSQL Database  1. Real-time Web Application  Use : Chat Apps, Social Feeds , Real-time analytics. Why NOSQL : Low Latency and High Throughput especially With in Memory database  2. Social Media Platform  Use : Paste , Like, Comment, User Relationship  Why NOSQL: Flexible Scheme Allows Fast change Grap Database are Great For Relationship 
Read more