A simple in-memory key/value store.
Memory KV store for Uploadista
Tomahawk plugin, implementing a Key Value Pair Store in Memory.
The Aztec KV store is an implementation of a durable key-value database with a pluggable backend. The only supported backend right now is LMDB by using the [`lmdb-js` package](https://github.com/kriszyp/lmdb-js).
Routes requests to KV assets
Memory / Redis abstraction for Directus
Invert the key/value of an object. Example: `{foo: 'bar'}` → `{bar: 'foo'}`
kv library - this library implements all the base functionality for NATS KV javascript clients
Isomorphic key-value storage with support for multiple backends
Fast, modern, in-memory key-value store for JavaScript. The perfect solution for caching in JavaScript.
Template project for writing node package with napi-rs
Template project for writing node package with napi-rs
HTTP server, in-memory store, plugin interface, and middleware for emulate service plugins.
A Deno KV client library optimized for Node.js.
Simple in-memory vinyl file store
DXOS key-value store.
High Performance In-Memory Cache for Node.js
In memory chunk store that is abstract-chunk-store compliant
MCP server for interacting with Cloudflare API
Apache Arrow columnar in-memory format
A simple CRUD based persistence abstraction for storing objects to any backend data store. eg. Memory, MongoDB, Redis, CouchDB, Postgres, Punch Card etc.
This library provides integration with NextAuth.js and TinaCMS including a NextAuth Credentials Provider for Vercel KV store.
WASM bindings for RuvLLM - browser-compatible LLM inference runtime with WebGPU acceleration
Persistent key-value store for web browsers backed by IndexedDB
Oria (oh-rye-uh) is an in-memory, Ruby-based Key-Value store. It's designed to handle moderate amounts of data quickly and easily without causing deployment issues or server headaches. It uses EventMachine to provide a networked interface to a semi-persistent KVS and asynchronously writes the in-memory data to YAML files.
Use Mysql AUTO_INCREMENT to support key value cache, which should be combined by an integer and string. It means to reduce the database storage size, and improve query performance. All cache will store in process memory, and will never be expired, until the process dies, so the less kvs you use, the better performance you will get. BTW, 100,000 general strings use 10MB memory. Some relatived articles: http://en.wikipedia.org/wiki/Correlation_database Usage ------------------------------------------ ## setup ```ruby create_table :kv_browser_names, :options => 'ENGINE=MyISAM DEFAULT CHARSET=utf8' do |t| t.string :name t.timestamps end class KvBrowserName < ActiveRecord::Base include IdNameCache end ``` or ```ruby create_table :common_tag, :options => 'ENGINE=MyISAM DEFAULT CHARSET=utf8' do |t| t.integer :tagid t.string :tagname end class CommonTag < ActiveRecord::Base self.table_name = :common_tag self.primary_key = :tagid include IdNameCache; set_key_value :tagid, :tagname # include IdNameCache; set_key_value_without_create :tagid, :tagname # if you dont want create it automately end ``` ### use cases ```text ruby-1.9.3-rc1 :001 > QuizTag[1] QuizTag Load (0.3ms) SELECT `common_tag`.* FROM `common_tag` WHERE `common_tag`.`tagid` = 1 LIMIT 1 => "Android" ruby-1.9.3-rc1 :002 > QuizTag[1] => "Android" ruby-1.9.3-rc1 :003 > QuizTag['Android'] QuizTag Load (0.5ms) SELECT `common_tag`.* FROM `common_tag` WHERE `common_tag`.`tagname` = 'Android' LIMIT 1 => 1 ruby-1.9.3-rc1 :004 > QuizTag['Android'] => 1 ``` == Copyright MIT, David Chen at eoe.cn
No description provided.
No description provided.
No description provided.