A fast, and lightweight DB for storing ordered data. The order it comes out is the order that it went in. The API is meant to be small and without bloated queries. Consequently, there is a limited set of queries to be made since the primary tool is getting objects in and out of storage in a specific order.

Because it is fast. And it is simple.

Let's say you want to have a chat or a news feed. The data will ALWAYS be displayed in the same order. Why not persist your data objects in the order you want them in?

MerkavaDB stores whatever data you need it to. It is schemaless. If you can transfer it, it will store.

By making TCP connection to the database server. All you need to do is specify a "channel" and some data. The protocol is simple:

<channel> <command> <extras>\n

Note, the line break at the end of the message is critical. As is the single spacing.

Your response will be:

OK <message>

or

ER <message>

A channel is a division of data. All data is stored in a sequential order for a given channel. For example, it could be a single chat room or news feed.

• PUSH - add a new item to the channel
• RETRIEVE - get a single item by id from the channel
• RECENT - get `n items from the channel
• UPDATE - change a single item
• DELETE - remove an item from a channel (not yet implemented)
• RESTORE - return a deleted item to the channel (not yet implemented)
• PURGE - cleanup all deleted items (not yet implemented)
• FLUSH - empty a channel
• BACKUP - persist a channel to disk
• STATS - receive information and stats about a channel

There currently is a proof of concept implementation out there. It is being rebuilt from the ground up in Rust. More to come later.