> ## Documentation Index > Fetch the complete documentation index at: https://cyborg-encryption-copy.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. # Backing Stores CyborgDB transforms traditional databases into Confidential Vector Databases by leveraging their storage capabilities while adding encrypted vector search functionality. Choose the backing store that best fits your existing infrastructure and operational requirements. CyborgDB RAG Overview ## PostgreSQL **Production-ready relational database with vector extensions** PostgreSQL provides robust data durability, ACID transactions, and excellent tooling ecosystem. CyborgDB leverages PostgreSQL's reliability while adding encrypted vector search capabilities on top. ### Key Benefits **ACID Compliance**\ Full transactional consistency for mission-critical applications with guaranteed data integrity. **Rich Ecosystem**\ Extensive tooling, monitoring, and operational expertise available across the industry. **Enterprise Scalability**\ Support for read replicas, connection pooling, horizontal scaling, and mature backup solutions. **Best For:** Production applications requiring data consistency, teams with existing PostgreSQL expertise, and environments requiring strict data durability guarantees. *** ## Redis **High-performance in-memory data store** Redis delivers ultra-low latency access patterns, making it ideal for real-time applications. CyborgDB uses Redis's memory-optimized storage for blazing-fast vector search operations. ### Key Benefits **Ultra-Low Latency**\ Sub-millisecond response times for vector queries with excellent concurrent access performance. **High Throughput**\ Optimized for high-volume concurrent operations with flexible data structures beyond simple key-value storage. **Configurable Persistence**\ Choose between speed and durability with flexible persistence and replication options. **Best For:** Real-time applications with strict latency requirements, high-throughput vector search workloads, and caching scenarios. *** ## Memory **Local in-process storage for development and testing** Memory-based storage keeps all data in local process memory, providing the fastest possible access with zero network overhead. Perfect for development, testing, and single-process applications. ### Key Benefits **Zero Network Latency**\ Direct memory access without serialization overhead for maximum performance. **Development Simplicity**\ No external dependencies or configuration required - instant setup for prototyping. **Deterministic Performance**\ Predictable access patterns with complete control over memory usage. **Best For:** Development and testing environments, single-process applications, proof-of-concept scenarios, and ephemeral data requirements. *** ## Standalone (for evaluation purposes only) **Built-in database for evaluation and testing** Standalone provides a self-contained database instance that starts automatically when no external database is configured. Perfect for quick evaluation, development, and testing without setting up external infrastructure. ### Key Benefits **Zero Configuration** Starts automatically when CYBORGDB\_DB\_TYPE is not set - no external database setup required. **Instant Setup** Begin evaluating CyborgDB immediately without infrastructure provisioning or configuration. **Best For:** Evaluation and testing, rapid prototyping, development environments, and learning CyborgDB features without infrastructure overhead. ### Important Limitations **Standalone is for EVALUATION PURPOSES ONLY** - It should NOT be used in production environments. For production deployments, use external Redis or PostgreSQL instances with proper persistence, replication, and backup strategies. *** ## Future Backing Stores CyborgDB is designed to be extensible, allowing for future backing stores to be added as needed. Have one in mind? [Let us know!](https://www.cyborg.co/contact) *** ## Managed Services Support CyborgDB works seamlessly with managed database services, reducing operational overhead while maintaining security and performance. **Amazon RDS for PostgreSQL**\ Fully managed PostgreSQL with automated backups and scaling **Amazon ElastiCache for Redis**\ Managed Redis with cluster mode and automatic failover **Azure Database for PostgreSQL**\ Managed PostgreSQL with built-in security and monitoring **Azure Cache for Redis**\ Enterprise-grade managed Redis with geo-replication **Cloud SQL for PostgreSQL**\ Fully managed PostgreSQL with automatic maintenance **Memorystore for Redis**\ Secure and highly available managed Redis service *** ## Choosing the Right Backing Store * **Data Durability** - You need guaranteed data persistence and consistency * **Complex Queries** - Your application requires SQL queries beyond vector search * **Team Expertise** - Your team has PostgreSQL operational knowledge * **Compliance** - You need audit trails and transaction logging * **Production Workloads** - Mission-critical applications requiring ACID guarantees * **Performance** - Sub-millisecond latency is critical to your application * **Scale** - You need to handle high concurrent query loads * **Real-time** - Your application provides real-time recommendations or search * **Caching** - You're implementing a high-performance caching layer * **Session Storage** - Temporary data with fast access requirements * **Development** - You're building and testing your application * **Single Process** - Your application runs in a single process or container * **Temporary Data** - Your vectors are computed on-demand and don't need persistence * **Simplicity** - You want to minimize external dependencies * **Maximum Performance** - Need absolute fastest access with zero network overhead * **Evaluation** - You're evaluating CyborgDB features and capabilities * **Quick Start** - You want to start immediately without setting up databases * **Testing** - You need a disposable database for integration testing * **Learning** - You're learning CyborgDB without infrastructure complexity * **Prototyping** - Building proof-of-concept with minimal setup overhead ## Configuration Examples ```python PostgreSQL theme={null} from cyborgdb_core import DBConfig # Local PostgreSQL db_config = DBConfig("postgres://user:password@localhost:5432/cyborgdb") # Amazon RDS db_config = DBConfig("postgres://user:password@rds-endpoint.region.rds.amazonaws.com:5432/cyborgdb") ``` ```python Redis theme={null} from cyborgdb_core import DBConfig # Local Redis db_config = DBConfig("redis://localhost:6379") # Redis with authentication db_config = DBConfig("redis://:password@redis-host:6379") # AWS ElastiCache db_config = DBConfig("redis://elasticache-endpoint.region.cache.amazonaws.com:6379") ``` ```python Memory theme={null} from cyborgdb_core import DBConfig # In-memory storage (no external dependencies) db_config = DBConfig("memory") ``` ```python Standalone theme={null} from cyborgdb_core import DBConfig # Standalone is used automatically when no DB type is set # No configuration needed - starts automatically in the service # Data stored in ~/.cyborgdb/standalone.db # Note: Standalone is only available in CyborgDB Service, # not in the embedded library ``` ## Performance Characteristics | Backing Store | Latency | Throughput | Durability | Consistency | | -------------- | :-----: | :--------: | :----------: | :-------------------: | | **Memory** | \~1µs | Very High | None | Single Process | | **Standalone** | \~100µs | Medium | Local Disk | Eventually Consistent | | **Redis** | \~100µs | High | Configurable | Eventually Consistent | | **PostgreSQL** | \~1ms | Medium | Full | ACID | Choose based on your application's specific requirements for speed, durability, and consistency.