Merge pull request #6 from tidesdb/design-boards-additions

Adding some design board images to 'How does TidesDB work?'

Author: guycipher

public/column-family-board.png

@@ -42,6 +42,8 @@ A distinctive aspect of TidesDB is its organization around column families. Each
 
 This design allows for domain-specific optimization and isolation between different types of data stored in the same database.
 
+![](/column-family-board.png)
+
 ## 4. Core Components and Mechanisms
 ### 4.1 Memtable
 The memtable is an in-memory data structure that serves as the first landing point for all write operations. Key features include:
@@ -58,6 +60,8 @@ SSTables are the immutable on-disk components of TidesDB. Their design includes:
 - **Min-Max Key Range**: Each SSTable stores the minimum and maximum keys it contains to optimize range queries. This block lives at block 0
 - **Immutability**: Once written, SSTables are never modified (only eventually merged or deleted)
 
+![](/sst-block-format-board.png)
+
 ### 4.3 Write-Ahead Log (WAL)
 For durability, TidesDB implements a write-ahead logging mechanism:
 
@@ -134,6 +138,8 @@ TidesDB implements two distinct compaction strategies:
 - Blocks less than manual compaction
 - Continues until system shutdown
 
+![](/sst-pair-merge-board.png)
+
 ### 6.3 Compaction Mechanics
 During compaction:
 
@@ -143,6 +149,8 @@ During compaction:
 4. Tombstones (deletion markers) and expired TTL entries are purged
 5. Original SSTables are deleted after successful merge
 
+![](/sst-pair-merge-tombstone-board.png)
+
 ## 7. Performance Optimizations
 ### 7.1 Block Indices
 TidesDB employs block indices to optimize read performance: