evoid-smart-storage

Multi-DB routing — Intent Handler system

Quick Start • Intent Handler • Routing • API

Quick Start

uv add evoid-smart-storage

Method 1: Intent Handler (Recommended)

from evoid_smart_storage import register_handlers
from evoid.core.storage import storage_read, storage_write

# Register Smart Storage as storage handler
register_handlers(config={
    "mapping": {
        "credentials": "postgresql",
        "session": "redis",
        "logs": "memory",
    },
})

# Routes automatically based on data type
await storage_write("cred:db_pass", {"password": "secret"})
await storage_write("session:abc", {"user": "alice"})

Method 2: Direct API

from evoid_smart_storage import SmartStorage

storage = SmartStorage(config={...})
await storage.write("key", {"data": "value"})

Intent Handler

evoid-smart-storage registers these Intent handlers:

Routing

Smart Storage routes data based on:

1. Data type — credentials → PostgreSQL, sessions → Redis
2. Intent level — CRITICAL → PostgreSQL, STANDARD → SQLite
3. User ID — multi-tenancy support
4. Metadata override — explicit backend selection

Configuration

TOML

[engines]
storage = "smart_storage"

[engines.options.smart_storage]
mapping = { credentials = "postgresql", session = "redis" }

API

register_handlers(config: dict)

Register Smart Storage as Intent handlers.

SmartStorage Methods

How It Works

Smart Storage reads the mapping config and routes each key to the correct backend:

• credentials → PostgreSQL (sensitive data)
• session → Redis (ephemeral)
• logs → Memory (debug)

Level routing sends CRITICAL Intents to PostgreSQL, STANDARD to SQLite. Your handler code never sees the routing logic.

Dependencies

• evoid>=0.4.0
• At least one storage plugin (sqlite, postgresql, redis, etc.)

Links

• EVOID Runtime
• Documentation
• Plugin Collection

License

MIT