Skip to content

Latest commit

 

History

History
73 lines (46 loc) · 3.4 KB

README.md

File metadata and controls

73 lines (46 loc) · 3.4 KB

spiderq server

Summary

Fast standalone priority queue / KV database with simple zeromq-based binary protocol.

It is supposed to be a part of some schedule related software (web crawlers, monitoring, pollers, status checkers, etc).

Initially has been develloped for Kribrum project.

Building spiderq

Get spiderq

% git clone https://github.com/swizard0/spiderq.git
% cd spiderq
% git submodule init
% git submodule update

Compile binary

Requirements:

% cargo build --release

After successfull building the binary should be in target/release/spiderq directory.

Running spiderq

Command line parameters

Usage: target/release/spiderq

Options:
    -d, --database      database directory path (optional, default: ./spiderq)
    -l, --flush-limit   database disk sync threshold (items modified before
                        flush) (optional, default: 131072)
    -z, --zmq-addr      zeromq interface listen address (optional, default:
                        ipc://./spiderq.ipc)

Existing protocol implementations

Design.

Spiderq creates a socket of ZMQ_ROUTER type for external communication and binds it to the address given in --zmq-addr command line parameter. So clients should connect it using ZMQ_REQ (usually), ZMQ_DEALER or ZMQ_ROUTER sockets.

Protocol uses simple request-reply schema (synchronous). Both requests and replies are encoded according to specifications in last frame of zeromq message. Spiderq server can handle any number of frames in message: all of them except the last one will be returned to the client back, and the last frame will be the actual server reply. This allows a client to pass arbitrary information with requests, for example, cookies, authentication, state or some internal routing data (see espiderq implementation).

License

The MIT License (MIT)

Copyright (c) 2016 Alexey Voznyuk

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.