Search Results for "filesystem"

...And designed to hold small amounts of data that can fit entirely in memory. Read and write values using standard HTTP tools, such as curl. Store data in hierarchically organized directories, as in a standard filesystem. Watch specific keys or directories for changes and react to changes in values.

...A Jepsen-style bank test runs nightly for 8h, with --race flag and ensures the maintenance of transactional guarantees. Badger has also been tested to work with filesystem-level anomalies, to ensure persistence and consistency. Badger is being used by a number of projects including Dgraph, Jaeger Tracing, UsenetExpress, and many more. BadgerDB is a pretty special package from the point of view that the most important change we can make to it is not on its API but rather on how data is stored on disk.

...The Database Lab Engine (DLE) runs on an independent server within your own infrastructure. The engine stores a single, full-size copy of production data on the specialized ZFS filesystem. Using the copy-on-write capabilities of ZFS, the DLE is able to generate full-size replicas of the production database in seconds. These writable "thin clones" will behave identically to production: they will have the same data and generate the same query plans. Instances of the Database Lab Engine (DLE) and all thin clones reside completely within your own infrastructure at all times.

redix is a very simple key => value storage engine that speaks redis and even more simpler and flexible. redis is very simple, sometimes we abuse it, so I decided to build a pure key-value storage system that introduces the core utilities for building any data structure you want based on the key => value model that is because I think that everything could be modeled easily using that model, so I decided to not to follow redis and all of its commands, you won’t find lpush, hset, sadd, … etc...