node.js ko
Noozer
Noozer
by rescue failover
It supplies a simple server side JS-API as well as a REST-API to talk to Doozer servers and a small admin webapp to manipulate the data in the Doozer servers from the browser. (Doozer is a high availability NoSQL data store.)
Judging Instructions
Go to rescue-failover.nko2.nodeknockout.com/ to access the admin gui. The different actions allow for saving, deleting and listing contents of the Doozer cluster running in the backend behind the webapp.
To look at the JS-API go to: https://github.com/nko2/rescue-failover.
Who
froderik — Stockholm
dahankzter
How
We use Doozerd of course since its the actual data storage. We currently use the client api as well since there was simply not enough time to finish the protocol buffer communication that Doozer uses. The two webapps are currently deploy in a loadbalanced fashin behind Nginx.
- Doozerd (https://github.com/ha/doozerd/)
- Doozer (https://github.com/ha/doozer/)
- Optimist (https://github.com/substack/node-optimist/)
- RSpec (http://relishapp.com/rspec/)
- Nginx (http://nginx.org/)
Votes
Your Vote
Voting is now closed.
Other Votes
therazorbladejudge
landlessnessjudgeseemed like a pretty basic set of capabilities without a very thoughtful design.
RafaelCorralesjudge
mikealjudgedylang
contestantIt might help the real judges if you explain what Doozer is and why there is a need for this.
mperham
judgeHas potential to be very useful. Missing anything that could be remotely called design and any sort of security. Very buggy creating new keys with values.
paularmstrong
contestant
henrikberggrenjudgeAlways great with JS API’s to datastores. Never tried Doozer though
I have never used Doozer before so can’t really tell how useful or innovative this is. Assuming it is a common data store, this interface is probably only useful for very small sets. Beyond that, it will be impossible to really admin a large database without some basic query and filtering features.
The JS-API link is probably private.