How aerospike/aerospike-server works
Main Components
a. Core Server Components:
• Base System (/as/src/base)
• Fabric Layer (/as/src/fabric)
• Storage Engine (/as/src/storage)
• Transaction Processing (/as/src/transaction)
• Query Engine (/as/src/query)
• Secondary Index (/as/src/sindex)
• Geospatial Processing (/as/src/geospatial)
b. Supporting Infrastructure:
• Common Foundation (cf/) - Contains core utilities
• External Dependencies (modules/)
• Configuration Management
• Security Layer
┌─────────────────────────────────────────────┐
• Client Interface │
• ┤
• Query & Transaction Layer │
• ┤
• Distribution Layer │
• (Clustering, Fabric, Partition Balance) │
• ┤
• Storage Engine │
• (Memory, SSD, Index Management) │
• ┤
• Common Foundation (CF) │
• ┘
Specific Elements to Highlight
a. Distribution Mechanism:
• Clustering system
• Fabric communication
• Partition management
• Migration handling
b. Storage Options:
• Memory-based storage
• SSD storage
• Index management
• Flat storage
c. Transaction Processing:
• Read/Write paths
• Delete operations
• UDF execution
• Duplicate resolution
Additional Details
Callouts for:
• Security features
• Configuration management
• Monitoring and health checks
• Backup and recovery paths
Integration Points
Connections to:
• External modules (Lua, S2 Geometry, etc.)
• Client libraries
• Management interfaces
Performance Critical Paths
• Main read path
• Main write path
• Query execution flow
• Index update flow
Scaling Aspects
Annotations for:
• Cluster expansion points
• Data distribution mechanisms
• Load balancing components
• Replication paths
This design should reflect Aerospike's key objectives of high performance, reliability (ACID properties), and operational efficiency, while showing how the various components work together to achieve these goals.