Node.js client for Cloudflare's KV Storage: a global, highly distributed, low-latency, key-value data store.
Persistent, verifiable memory for AI agents — backed by 0G Storage (KV + Log) and 0G Chain
Shopify App Session Storage for KV
Cloudflare-native storage (KV) and uploads (R2) adapters for CaretCMS.
Routes requests to KV assets
Invert the key/value of an object. Example: `{foo: 'bar'}` → `{bar: 'foo'}`
Isomorphic key-value storage with support for multiple backends
kv library - this library implements all the base functionality for NATS KV javascript clients
Redis storage for grammy library.
Seamlessly integrate better-auth with Cloudflare Workers, D1, Hyperdrive, KV, R2, and geolocation services.
Memory / Redis abstraction for Directus
A promise that is resolvable (or rejectable) after it was created.
Encrypted put and get functions for Cloudflare Workers KV
TypeScript SDK for Alien bindings - gRPC client for Storage, KV, Queue, Vault, and more
Redis KV adapter for Payload
The next generation web framework for Cloudflare Workers
Utility functions for the workspace
Key-value storage integration for MPLP
A Deno KV client library optimized for Node.js.
Unstorage driver for integration with SCAYLE PaaS
Core apps for AI agents — database, storage, KV, and more. All local, zero external dependencies.
Simple abstract key-value json database
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).
A Deno KV client library optimized for Node.js
Tarantool KV-storage client.
KV Storage As a Service, LOLz
Tarantool KV-storage ActiveModel-aware Record.
API for Functions, Queues, KV, Storage, Cron, and Scheduler.
Library for interacting with Cloudflare Workers KV Storage and configuring connection from a Rails application.
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.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.