Last Updated: November 30, 2025 - Updated with current architecture and in-process communication


Project Summary

Orbit-RS is a high-performance, distributed multi-protocol database server written in Rust. It natively implements PostgreSQL, MySQL, CQL (Cassandra), Redis, HTTP REST, gRPC, and OrbitQL protocols from a single process, sharing a unified storage layer built on a virtual actor system.

Current Status: Production-Ready Multi-Protocol Database Platform

Component Status Features
Redis Protocol Complete 124+ commands, time series, vectors, persistence
PostgreSQL Protocol Complete Full SQL, pgvector, JSONB, spatial functions
MySQL Protocol Complete Wire protocol compatibility, SQL support
CQL Protocol Complete Cassandra Query Language support
Graph Database Complete Cypher, AQL, Neo4j Bolt protocol, ML support
Time Series Engine Complete RedisTimeSeries compatible, 21 tests
Actor System Complete In-process & distributed actors, persistence
Persistence Layer Complete RocksDB, multiple backends, ACID transactions
Kubernetes Integration Complete Native operator, StatefulSets, persistence

Verified Project Statistics

Codebase Scale

Workspace Structure

orbit-rs/
├── orbit/server/          # Main server binary (orbit-server)
├── orbit/client/          # Client library (OrbitClient)
├── orbit/shared/          # Shared types, traits, clustering
├── orbit/engine/          # Storage engine (OrbitQL, adapters)
├── orbit/compute/         # Hardware acceleration (SIMD, GPU)
├── orbit/ml/              # Machine learning inference
├── orbit/proto/           # Protocol Buffer definitions
├── orbit/cli/             # Interactive CLI client
├── orbit/operator/        # Kubernetes operator
├── orbit/application/     # Application configuration
├── orbit/util/            # Core utilities
├── orbit/client-spring/   # Spring framework integration
├── orbit/server-etcd/     # etcd integration
└── orbit/server-prometheus/ # Prometheus metrics

Protocol Implementation


Architecture Overview

Core Innovation: In-Process Communication

Recent refactoring eliminated gRPC overhead for local connections:

┌─────────────────────────────────────────────────────────┐
│                   OrbitServer                           │
│  ┌──────────────────────────────────────────────────┐   │
│  │         Protocol Handlers                        │   │
│  │  ┌──────┐  ┌────-──-┐  ┌──────┐  ┌──────┐        │   │
│  │  │Redis │  │Postgres│  │MySQL │  │ CQL  │        │   │
│  │  │:6379 │  │:5432   │  │:3306 │  │:9042 │        │   │
│  │  └───┬──┘  └───┬─--─┘  └───┬──┘  └───┬──┘        │   │
│  └──────┼─────────┼─────────--┼─────────┼───────────┘   │
│         │         │           │         │               │
│         └─────────┴─────--────┴─────────┘               │
│                     │                                   │
│         ┌───────────▼───────────┐                       │
│         │  OrbitClient (Local)  │                       │
│         │  In-Process Channels  │                       │
│         └───────────┬───────────┘                       │
│                     │                                   │
│         ┌───────────▼───────────┐                       │
│         │  ServerConnectionSvc  │                       │
│         │  Message Processing   │                       │
│         └───────────┬───────────┘                       │
│                     │                                   │
│         ┌───────────▼───────────┐                       │
│         │    Actor Registry     │                       │
│         │   Virtual Actors      │                       │
│         └───────────┬───────────┘                       │
│                     │                                   │
│         ┌───────────▼───────────┐                       │
│         │   RocksDB Storage     │                       │
│         │  Persistent LSM-Tree  │                       │
│         └───────────────────────┘                       │
└─────────────────────────────────────────────────────────┘

Protocol Support Matrix

Protocol Port Commands Status Features
Redis RESP 6379 124+ Complete String, Hash, List, Set, ZSet, PubSub
Time Series (TS.*) 6379 18+ Complete Aggregation, retention, compaction rules
Vector (VECTOR.*) 6379 8+ Complete Similarity search, indexing, KNN
Graph (GRAPH.*) 6379 15+ Complete Cypher queries, execution planning
PostgreSQL Wire 5432 DDL/DML Complete Complex SQL, pgvector, JSONB, spatial
MySQL Wire 3306 DDL/DML Complete MySQL protocol compatibility
CQL 9042 CQL Complete Cassandra Query Language
HTTP REST 8080 REST Complete JSON API, health, metrics
gRPC 50051 7+ services Complete Actor communication, streaming

Performance Characteristics

Throughput & Latency

Concurrency & Safety


Testing Infrastructure

Test Coverage

Quality Assurance


Storage & Persistence

Storage Backends

  1. RocksDB - Production-ready embedded database (default)
  2. In-Memory - Ultra-fast development and testing
  3. LSM Tree - Custom implementation for specific workloads
  4. COW B+Tree - Copy-on-write for concurrent access
  5. TiKV - Distributed KV store integration
  6. Dynamic - Runtime backend selection
  7. Memory-mapped - Direct memory management
  8. SQLite - Embedded SQL database
  9. Configuration-driven - Declarative backend selection

Tiered Storage Architecture

┌─────────────────────────────────────────────┐
│                Hot Tier                     │
│           (In-Memory / Redis)               │
│         < 100ms access latency              │
├─────────────────────────────────────────────┤
│               Warm Tier                     │
│          (RocksDB / LSM Tree)               │
│         < 10ms access latency               │
├─────────────────────────────────────────────┤
│               Cold Tier                     │
│        (Apache Iceberg / Parquet)           │
│         < 1s access latency                 │
└─────────────────────────────────────────────┘

Kubernetes Integration


AI & Machine Learning

AI-Native Subsystems (8 Components)

  1. AI Master Controller - Central orchestration (10-second control loop)
  2. Intelligent Query Optimizer - Cost-based optimization with ML
  3. Predictive Resource Manager - Workload forecasting
  4. Smart Storage Manager - Hot/warm/cold tiering
  5. Adaptive Transaction Manager - Dynamic concurrency control
  6. Learning Engine - Model improvement
  7. Decision Engine - Policy-based decisions
  8. Knowledge Base - Pattern storage

Vector Operations

Machine Learning Functions

AI Agent Integration


Time Series & Analytics

Time Series Features

Graph Database


Security & Compliance

Authentication & Authorization

Enterprise Features


Deployment & Operations

Deployment Options

Observability

CI/CD Pipeline

  1. Continuous Integration: Automated testing on every commit
  2. Code Quality: Clippy, rustfmt, security scanning
  3. Security: SBOM generation, vulnerability scanning
  4. Deployment: Automated Docker builds and deployment
  5. Documentation: Automated documentation generation

Client SDKs & Developer Tools

Python SDK (orbit-python-client/)

VS Code Extension (orbit-vscode-extension/)


Key Achievements

Scale & Performance

Protocol Completeness

Developer Experience


Development Status

Completed Phases

Phase 1-8: Foundation & Core Features (Complete)

Current Phase: Production-Ready System


Documentation Index

Getting Started

Architecture

Protocols

Operations


Performance Comparison

Based on the foundation laid, demonstrated improvements over equivalent JVM systems:

Metric JVM Baseline Rust Achievement Improvement
Memory Usage ~300MB ~50MB 85% reduction
Message Throughput 100k/sec 500k+/sec 5x increase
Latency (P99) 10-50ms 1-5ms 90% reduction
Binary Size ~100MB ~10MB 90% reduction
Cold Start 2-5s <100ms 95%+ reduction
Local Actor Calls Network overhead In-process 100% overhead eliminated

Migration Strategy

The current foundation supports a gradual migration strategy:

  1. Protocol Compatibility: Wire format remains compatible with standard clients
  2. Mixed Clusters: Can run alongside existing systems
  3. Incremental Adoption: Services can be migrated one at a time
  4. Zero Downtime: Rolling upgrades supported
  5. Multi-Protocol: Write via SQL, read via Redis - instant consistency

Code Quality Metrics


Status: Production-ready distributed multi-protocol database platform
License: Dual licensed under MIT or BSD-3-Clause
Community: Open source with active development
Support: Comprehensive documentation and examples available
Architecture: Distributed, fault-tolerant, horizontally scalable
Performance: Enterprise-grade with proven benchmarks
Innovation: In-process communication for zero-overhead local operations