npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

cruise-db

v0.0.2

Published

An example k/v store based upon cruise

Downloads

4

Readme

cruise-db

A reference k/v store based upon cruise. It's the javascript analog to goraft/raftd.

Usage

To get a server running you'll want to run the server:

$ npm install -g cruise-db
$ cruise-db --port 4001
listening on 4001...

Then you can store values by posting to /db/:key

$ curl http://localhost:4001/db/some-key \
    -X POST \
    --data 'foo=bar'

And get them back from /db/:key

$ curl http://localhost:4001/db/some-key
{"foo":"bar"}

Clustering

Since the whole point of raft is consensus among a distributed system, the reference db can be run as a cluster. Simply pass the --join [-j] option with the connection string of the leader to add servers to the cluster

$ cruise-db
Listening on 4001...

$ cruise-db --port 4002 --join localhost:4001
Listening on 4002...

$ cruise-db --port 4003 --join localhost:4001
Listening on 4003...

You can query keys from the followers and they should stay in sync with any new keys posted to the leader.

Caveats

Just like raftd, the system does not do any sort of client forwarding. In order to submit new commands, you will have to post them to the leader node.

License

(The MIT License)

Copyright (c) 2014 Calvin French-Owen <[email protected]>

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.