tigrbl_engine_memkv

In-memory key-value engine plugin for process-local KV storage, cache workflows, and lightweight Tigrbl services.

What is tigrbl_engine_memkv?

In-memory key-value engine plugin for process-local KV storage, cache workflows, and lightweight Tigrbl services.

Why use tigrbl_engine_memkv?

Use it when a Tigrbl application needs this backend without installing every engine package.

When should I install tigrbl_engine_memkv?

Install it when the storage, analytics, cache, or integration workload named by this package is the intended runtime backend.

Who is tigrbl_engine_memkv for?

Application developers, data platform engineers, and operators choosing concrete persistence or data-plane behavior.

Where does tigrbl_engine_memkv fit?

tigrbl_engine_memkv lives at pkgs/engines/tigrbl_engine_memkv and serves process-local in-memory runtime behavior.

How does tigrbl_engine_memkv work?

It exposes a tigrbl.engine entry point and a package register() hook so Tigrbl can discover or load the backend at runtime.

Certification Status

• Package status: governed package in the tigrbl/tigrbl workspace.
• Governance source: SSOT registry.
• Release evidence: publish workflow validates package builds, tests, GitHub release assets, and PyPI publication for managed packages.
• Local certification guard: pkgs/core/tigrbl_tests/tests/unit/test_package_badges_and_notices.py verifies every package README keeps the Discord badge, Apache 2.0 badge, explicit Python-version badge, LICENSE, and NOTICE.
• Scope note: this README documents the package boundary. Runtime feature support remains governed by .ssot/ entities and the conformance docs linked below.

Install

uv add tigrbl_engine_memkv

pip install tigrbl_engine_memkv

Surface Coverage

What It Owns

tigrbl_engine_memkv owns the engine plugin boundary. It should be installed when you need this package's focused responsibility without assuming every other Tigrbl workspace package is present.

Implementation orientation:

• tigrbl_engine_memkv: kv, plugin, session

Public API and Import Surface

• Import roots: tigrbl_engine_memkv.
• Public symbols: __version__.
• Workspace dependencies: tigrbl.
• External runtime dependencies: none declared.

Usage Examples

Verify the installed package

python -m pip show tigrbl_engine_memkv
python - <<'PY'
from importlib.metadata import version
print(version("tigrbl_engine_memkv"))
PY

Register the engine plugin explicitly

from tigrbl_engine_memkv.plugin import register

register()

Discover the engine through package metadata

from importlib.metadata import entry_points

for entry_point in entry_points(group="tigrbl.engine"):
    if entry_point.module.startswith("tigrbl_engine_memkv"):
        plugin_register = entry_point.load()
        plugin_register()

Install alongside the facade

uv add tigrbl tigrbl_engine_memkv
pip install tigrbl tigrbl_engine_memkv

How To Choose This Package

Choose tigrbl_engine_memkv when the quick-answer table matches your use case. Choose tigrbl instead when you want the full public facade. Choose a lower-level package such as tigrbl-core, tigrbl-base, or tigrbl-runtime when you are building framework extensions or testing a specific internal boundary.

Related Packages

• tigrbl
• tigrbl-core
• tigrbl-runtime
• tigrbl_engine_sqlite
• tigrbl_engine_postgres
• tigrbl_engine_duckdb
• tigrbl_engine_pandas

Documentation Links

• Workspace docs
• Package catalog
• Package layout
• Current target
• Current state
• SSOT registry
• Release workflow

Support

• Community: Discord.
• Issues: GitHub Issues.
• Repository: pkgs/engines/tigrbl_engine_memkv.

Package-local Boundary

This README is the package-local distribution entry point for tigrbl_engine_memkv. It answers install, usage, API, ownership, and certification-orientation questions for this package. Broader architectural decisions, release status, and cross-package proof chains remain in the repository-level docs and SSOT registry.

License

Licensed under the Apache License, Version 2.0. See LICENSE, NOTICE, and the official Apache 2.0 license text.