Lately, I've been working on pgDOWN, which is a Postgres backend for levelup, so that I can support Postgres in Dulcimer. My motivation is to have a CP backend for Duclimer. Currently leveldb (levelDOWN) works great for an embedded backend, and Riak for an AP backend, but I we ...
While developing the prototype for what became @quitlahok's riakdown, I quickly realized that while Riak can give keys back in lexical order of indexes, it cannot do the same in reverse. We needed reverse support in order to support the levelup interface.
Our solution was to generate extra indexes ...
Riak is a clustered key-value database that applies "AP" from the CAP Theorem. It has HTTP and Protocol Buffers APIs, but can be a little bit cumbersome to browse keys for debugging. I've been getting used to hij1nx's lev for debugging levelup and thought it would be handy ...
Redis is nice for dealing with data as it is relevant and changing, but once it goes a little stale, you probably want to archive it to free up resources. Wouldn't it be nice to be able to archive it and still be able to query it?
Using my ...
Sometimes you'd rather images loading into your page don't show up until they're finished. Sometimes you don't have direct control over when images get added to your page.
The MutationObserver is a handy API for reacting when DOM changes within an element. It's commonly used ...
Yesterday I mentioned that you should maintain a lookup hash as you update keys.
So today, I decided to put that together. The only real gotcha is deleting the lookup to the old attribute value before updating the lookup hash.
Largely the same caviates apply as yesterday. We could flesh ...
Using a keystore efficiently is all about anticipating how the data will be looked up. If you can't do that, you may be better using a relational database.
Generating lookup tables and indexes can be helpful for finding the key you're looking for. For example, if you store ...
One of the cool things about Redis Lua scripting is the ability to publish notifications of your changes atomically with those changes made. There's actually a new Redis feature that can do this for you if configured: keyspace notifications. But maybe you want to send out a single notification ...
Any Redis command that returns key/value pairs returns the results as a single list of alternating keys and values. If you need to work the results in a Lua script, you'll likely want to collate them in a Lua table.
This script takes a Hash key and returns ...
See the update at the bottom: this approach isn't secure (but I still think it's interesting).
Storing passwords in plain text is bad. Time and time again, databases get hacked and passwords get leaked. Hashing a password creates a consistent string from a password that you can store ...