ArchGen

DBMS Architecture Diagram

Focus: Query Processor + Storage Engine. Key areas: JDBC, ODBC, Connection Pool.

Use this as a block diagram of the system when explaining architecture.

Preview
Edit this example
Diagram caption: DBMS Architecture Diagram (Query Processor + Storage Engine) has 4 layers: Client & SQL Interface, Query Processor, Storage Engine, Transactions & Recovery.

Prompt

DBMS architecture diagram for a relational database system. Clients connect via JDBC/ODBC and submit SQL. The query processor handles parsing, rewriting, cost-based optimization, and execution planning. The storage engine manages buffer cache, indexes, and file layout, while the transaction manager enforces ACID with MVCC and write-ahead logging. Include system catalog metadata, backup/restore, and monitoring. Show how queries flow through parser, optimizer, and execution engine to storage.
Highlights
  • Layer details · Query Processor: Modules include Parser & Rewriter, Optimizer, Execution Engine.
  • Layer details · Client & SQL Interface: Modules include Client Drivers, SQL Gateway, Admin Console.
  • Module responsibilities · Client & SQL Interface / SQL Gateway: Validate queries; Route statements; Enforce permissions

Overview

DBMS Architecture Diagram (Query Processor + Storage Engine) has 4 layers: Client & SQL Interface, Query Processor, Storage Engine, Transactions & Recovery.

Layer details

Show all (4)
  • Client & SQL Interface: Modules include Client Drivers, SQL Gateway, Admin Console.
  • Query Processor: Modules include Parser & Rewriter, Optimizer, Execution Engine.
  • Storage Engine: Modules include Buffer Manager, Index Manager, File & Table Storage.
  • Transactions & Recovery: Modules include Transaction Manager, Write-Ahead Log, Catalog & Backup.

Module responsibilities

Show all (12)
  • Client & SQL Interface / Client Drivers: Accept SQL sessions; Manage connections; Handle retries
  • Client & SQL Interface / SQL Gateway: Validate queries; Route statements; Enforce permissions
  • Client & SQL Interface / Admin Console: Manage metadata; Control privileges; Trigger backups
  • Query Processor / Parser & Rewriter: Normalize queries; Apply rules; Prepare for planning
  • Query Processor / Optimizer: Select plans; Reduce cost; Choose indexes
  • Query Processor / Execution Engine: Run query plans; Stream results; Manage memory
  • Storage Engine / Buffer Manager: Cache hot pages; Flush writes; Reduce I/O
  • Storage Engine / Index Manager: Maintain indexes; Speed lookups; Track usage
  • Storage Engine / File & Table Storage: Persist data files; Optimize storage; Manage tables
  • Transactions & Recovery / Transaction Manager: Ensure ACID; Manage concurrency; Detect conflicts
  • Transactions & Recovery / Write-Ahead Log: Guarantee durability; Recover from crashes; Support replication
  • Transactions & Recovery / Catalog & Backup: Store metadata; Enable planning; Recover data

Key flows

Show all (3)
  • Query flow: SQL statements are parsed, optimized, and executed; the execution engine reads pages from the buffer manager and indexes from the storage engine.
  • Transaction flow: MVCC and locks coordinate concurrent writes, while WAL records changes for recovery and replication.
  • Maintenance flow: catalog stats and backups are updated on schedule to keep query planning accurate and recovery reliable.