Centralised and Client server DBMS Architecture

Duration: 6 min

This video lesson is available to enrolled students.

Return to /learn/COGNIZANT-PREPARATION/dbms/basics-of-dbms/data-model-architecture-components/asset-centralised-and-client-server-dbms-architecture after enrolling

Inside: a video lesson and guided study material.

Module outline

  1. Communication Round: Vocabulary, Subject Verb Agreement (Verb Noun Agreement), Tenses, Comprehension / Reading Comprehension / Unseen Passages (Critical Reasoning) (Paragraph Questions), Cloze Test (Cloze Passage), Sentence Correction (Error Correction), Sentence Completion (Fill in the blanks), Sentence Re-arrangements (Para Jumbles) (Narrative Sequencing), Direct and Indirect Speech, Active Passive Voice (Voice), Verbal Analogy (Word Based Analogy), Articles, Preposition, Conjunction, Sentence Construction, English Writing Ability, Communication Assessment
  2. Quantitative Aptitude: Ratio and Proportion (Ratios), Divisibility Rules, Data Interpretation, Mixture and Alligation, Permutation and Combination, Logarithm, Number System, HCF LCM, Speed Time and Distance, Percentage, Average, Powers and Exponents (Surds and Indices), Time and Work, Mensuration and Geometry, Age Problems, Pipe and Cistern, Probability, Profit and Loss, Simple Interest and Compound Interest, Algebra
  3. Analytical and Logical Reasoning: Series (Number and Letter Series) (Numerical Relations and Reasoning), Coding Decoding, Data Sufficiency, Non Verbal Reasoning (Spatial Aptitude) (Spatial Reasoning) (Visual Reasoning), Directions (Direction Test), Ranking, Order and Sequence, Deductive and Inductive Reasoning (Logical Deduction and Induction) (Prepositional Reasoning), Selection Decision Table (Decision Making), Logical Sequence Of Words, Puzzle Solving (Puzzles), Syllogisms, Seating Arrangements, Calendar, Clock, Blood Relations, Cubes & Dices, Venn Diagram, Analytical Reasoning (Counting Figures Reasoning)
  4. Cognizant Gaming Aptitude: Gamified / Game Based Aptitude
  5. Java (Cluster 1): Java
  6. ANSI SQL MySQL (Cluster 1,2,3): SQL
  7. HTML, CSS, JavaScript (Cluster 1,3): HTML, CSS, JavaScript
  8. Python (Cluster 2): Python for Placements by Yash Sir
  9. Cloud Fundamentals (Cluster 2): Emerging Tech Trends
  10. C# (Cluster 3): C#
  11. OOPs: Object Oriented Programming (OOPS)
  12. Technical Assessment (Coding): Coding Questions by Yash Sir, C Programming by Yash Sir, Programming in C++, Pseudo Codes
  13. Data Structures: Introduction to DS, Array, Stack, Queue, Linked List, Tree, Graphs, Hashing
  14. DBMS: Basics of DBMS, ER Diagram, Relational Model & Functional Dependencies, Keys & Integrity Constraints, Normalization (1NF - BCNF), Decomposition Properties & 4NF, File Organization & Indexing, Relational Algebra, Relational Calculus, Transaction Management, Concurrency Control, Database Recovery, ORDBMS, Database Security & Authorization, Query Processing & Optimization, Enhanced Data Models, Data Warehousing & Mining, Big Data Systems, NoSQL
  15. Operating Systems: Introduction to OS, Process Management, CPU Scheduling, Process Synchronization, Deadlock, Threads & Process Creation, Memory Management, Virtual Memory, Disc Scheduling, File Management, Windows OS, Linux OS, Security, Distributed Systems, Virtual Machines
  16. Computer Networks: Introduction to CN, Data Communication, DLL: Access Control, DLL: Flow Control, DLL: Error Control, DLL: Framing, Data Link Layer - Ethernet, Net Layer: IPv4 & Proto, Net Layer: IP Addressing, Net Layer:Routing Protocol, Transport Layer Services, TL: Congestion & UDP, Application Layer, Hardware basics, Network Security, Mobile Technology, Cloud Computing and IoT, Cyber and Info Security
AI summary & chapters

AI Summary

An AI-generated summary of this video lecture.

The video presents a lecture on database management system (DBMS) architectures, focusing on centralized and client-server models. It begins by defining a centralized DBMS as a single system that integrates all components—DBMS software, hardware, application programs, and user interface processing software—into one location. The instructor explains that users can connect remotely via a terminal, but all processing occurs at the central site. This concept is visually reinforced with a hand-drawn diagram showing multiple terminals connected to a central processing unit labeled 'centralized'. The lecture then transitions to a more detailed, structured diagram titled 'A Physical Centralized Architecture' (Figure 2.4). This diagram illustrates the layered architecture, showing how terminals and monitors connect to a network, which in turn connects to the software layer (including DBMS, compilers, and application programs) running on an operating system. The operating system manages the hardware/firmware layer, which includes the CPU, memory, disk, and I/O devices. The instructor uses red annotations to highlight key components like 'Software', 'Operating System', and 'Hardware/Firmware', and to draw connections between the layers, emphasizing the flow of data and control in a physical centralized system.

Chapters

  1. 0:00 – 2:00 00:00-02:00

    The video opens with a slide titled 'Centralized and Client-Server DBMS Architectures'. The instructor defines a 'Centralized DBMS' as a system that combines all components—DBMS software, hardware, application programs, and user interface processing software—into a single system. The key point is that while users can connect through a remote terminal, all processing is done at the centralized site. The instructor begins to draw a simple diagram on the slide, sketching several terminal boxes at the bottom and a central box at the top, which will represent the centralized system.

  2. 2:00 – 5:00 02:00-05:00

    The instructor continues to build the diagram for the centralized architecture. He draws lines from the multiple terminal boxes to a central, larger box, which he labels 'centralized'. He then adds a downward arrow from the top of the central box, indicating that processing occurs there. The diagram visually represents the concept that multiple users (terminals) access a single, central processing unit. The instructor's hand is visible, actively drawing and annotating the diagram to illustrate the flow of interaction in a centralized system.

  3. 5:00 – 6:05 05:00-06:05

    The slide changes to a new diagram titled 'A Physical Centralized Architecture' (Figure 2.4). This detailed diagram shows the layered structure of a centralized system. The instructor uses red annotations to highlight the 'Software' layer (containing DBMS, compilers, application programs), the 'Operating System' layer, and the 'Hardware/Firmware' layer (including CPU, memory, disk, and I/O devices). He draws arrows to show the flow of data and control between these layers, emphasizing the physical connections and the hierarchical organization of the system components.

The lecture progresses from a conceptual definition of a centralized DBMS to a detailed physical architecture. It starts by explaining the core idea that all processing is centralized, even with remote users. This is then illustrated with a simple, hand-drawn diagram showing terminals connecting to a central unit. The lesson culminates in a more formal, structured diagram that breaks down the system into distinct layers—software, operating system, and hardware—showing how they interact to form a complete, physical centralized architecture. The progression demonstrates how a high-level concept is translated into a tangible, layered system design.

Loading lesson…