Home Explore Help
Sign In
ditsing
/
ruaft
1
0
Fork 0
Files Issues 0 Pull Requests 0 Wiki
Branch: master
Branches Tags
ruaft
/
durio
Jing Yang 93f6b20b3f Update dependencies. 9 months ago
..
src 23c826e6f9 Move raft code into its own directory. 2 years ago
Cargo.lock 93f6b20b3f Update dependencies. 9 months ago
Cargo.toml f5ff46482a Update Cargo.lock in durio. 2 years ago
README.md 27abdaee17 Add a README for durio. 4 years ago
build.sh 847feb248e Fix durio build after the project structure change. 2 years ago
curl.sh f3059b79ff Create a two-pi-plus-dev setup for durio. 4 years ago
pi-setup-notes.md b551bac311 Add Pi setup instructions. 4 years ago
run_smoke_test.sh 23c826e6f9 Move raft code into its own directory. 2 years ago
setup-build-debian.sh 4d0f07bc7e Add a script to prepare a debian machine to cross build durio. 2 years ago

README.md

durio

durio is a distributed KV store that comes with a simple HTTP interface. I run it on Raspberry Pis. In this repo you can find scripts (build.sh, curl.sh) and notes (pi-setup-notes) to help build, run and test durio on Raspberry Pis.

By default durio has 3 replicas. Each replica has a web server, a KV server and a raft instance behind it. The 3 web servers talk to all KV servers, while each KV server only talks to the raft instance in the same process.

durio relies on warp to provide the web server, and tarpc to run the RPC services.

Clients

Clients connected to one web server get a consistent (linearizable) view of the data stored in the KV store. The web servers can accept multiple incoming requests. At any given time, at most one request will be sent to the leading KV server. That limits the amount of data one web server can process.