Add detailed documentation explaining Brainy's 4-index architecture: - MetadataIndex: inverted indexing with temporal bucketing (v3.41.0) - HNSWIndex: hierarchical vector similarity search - GraphAdjacencyIndex: O(1) bidirectional relationship traversal - DeletedItemsIndex: soft-delete tracking Includes explanation of UnifiedCache for coordinated memory management across all indexes, integration patterns, performance characteristics, and best practices for developers. Updated overview.md to reference the new index architecture documentation.
5.2 KiB
5.2 KiB
Architecture Overview
Brainy is a multi-dimensional AI database that combines vector similarity, graph relationships, and metadata filtering into a unified query system. This document provides a comprehensive overview of the system architecture.
Core Components
Brainy (Main Entry Point)
The central orchestrator that manages all subsystems:
- 4-Index Architecture: MetadataIndex, HNSWIndex, GraphAdjacencyIndex, DeletedItemsIndex (see Index Architecture)
- Storage System: Universal storage adapters (FileSystem, S3, OPFS, Memory)
- Augmentation System: Extensible plugin architecture
- Triple Intelligence: Unified query engine
Triple Intelligence Engine
Brainy's revolutionary feature that unifies three types of search:
- Vector Search: Semantic similarity using HNSW indexing
- Graph Traversal: Relationship-based queries
- Field Filtering: Precise metadata filtering with O(1) performance
// Single query combining all three intelligence types
const results = await brain.find({
like: "machine learning papers", // Vector similarity
connected: { to: "research-team", depth: 2 }, // Graph traversal
where: { published: { $gte: "2024-01-01" } } // Metadata filtering
})
Storage Architecture
brainy-data/
├── _system/ # System management
│ └── statistics.json
├── nouns/ # Entity data storage
│ └── {uuid}.json
├── metadata/ # Metadata and indexing
│ ├── {uuid}.json
│ ├── __entity_registry__.json
│ └── __metadata_index__*.json
├── verbs/ # Relationship storage
└── locks/ # Concurrent access control
HNSW Index
Hierarchical Navigable Small World index for efficient vector search:
- Performance: O(log n) search complexity
- Memory Efficient: Product quantization support
- Scalable: Handles millions of vectors
- Persistent: Serializable to storage
Metadata Index Manager
High-performance field indexing system:
- O(1) Lookups: Inverted index for field→value→IDs mapping
- Query Support: equals, anyOf, allOf, range queries
- Chunked Storage: Supports massive datasets
- Auto-indexing: Automatically maintains indexes on updates
Performance Characteristics
Operation Complexity
- Vector Search: O(log n) via HNSW
- Field Filtering: O(1) via inverted indexes
- Graph Traversal: O(V + E) for breadth-first search
- Add Operation: O(log n) for index insertion
- Update Operation: O(1) for metadata updates
Memory Usage
- Base Memory: ~50MB for core system
- Per Vector: ~1KB (384 dimensions × 4 bytes)
- Index Overhead: ~20% of vector data
- Cache Size: Configurable (default 1000 entries)
Throughput
- Writes: 1000+ ops/second (with batching)
- Reads: 10,000+ ops/second
- Search: 100+ queries/second (varies by complexity)
Augmentation System
Brainy's extensible plugin architecture allows for powerful enhancements:
Core Augmentations
- Entity Registry: High-speed deduplication for streaming data
- Batch Processing: Optimized bulk operations
- Connection Pool: Efficient resource management
- Request Deduplicator: Prevents duplicate processing
Creating Custom Augmentations
class CustomAugmentation extends BrainyAugmentation {
async onInit(brain: Brainy): Promise<void> {
// Initialize augmentation
}
async onAdd(item: any, brain: Brainy): Promise<any> {
// Process item before adding
return item
}
}
Caching Strategy
Multi-layered caching for optimal performance:
- Search Cache: LRU cache for query results
- Metadata Cache: Field index caching
- Pattern Cache: NLP pattern matching cache
- Entity Cache: In-memory entity registry
Integration Points
Key Objects for Extensions
brain.index: Access HNSW vector indexbrain.metadataIndex: Access field indexingbrain.graphIndex: Access graph adjacency indexbrain.storage: Access storage layerbrain.augmentations: Access augmentation manager
For detailed information about each index, see Index Architecture.
Event System
brain.on('add', (item) => console.log('Item added:', item))
brain.on('search', (query) => console.log('Search performed:', query))
brain.on('error', (error) => console.error('Error:', error))
Best Practices
When Adding Features
- Check if similar functionality exists
- Consider if it should be an augmentation
- Use existing indexes and caches
- Avoid duplicating functionality
- Follow the established patterns
Performance Optimization
- Use batch operations for bulk data
- Enable appropriate caching
- Choose the right storage adapter
- Configure index parameters for your use case
- Monitor statistics for bottlenecks
Next Steps
- Index Architecture - Deep dive into the 4-index system
- Storage Architecture - Deep dive into storage system
- Triple Intelligence - Advanced query system
- API Reference - Complete API documentation