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 🙏

© 2026 – Pkg Stats / Ryan Hefner

alldata-peer-client-http

v0.1.2

Published

AllData Peer HTTP client module

Readme

alldata-peer-client-http

Stability: 1 - Experimental

NPM version

Peer Client HTTP module for AllData, a distributed master-less write-once immutable event store database implementing "All Data" part of Lambda Architecture.

Usage

var AllDataPeerClient = require('alldata-peer-client-http');
var AllDataKeygen = require('alldata-keygen');

var allDataPeerClient = new AllDataPeerClient({
    method: "POST",
    path: "/_put",
    port: 80 
});

var event1 = {customer: 1, action: "site visit"};
var key1 = AllDataKeygen.createKey();

allDataPeerClient._put({hostname: "first.peer.com"}, key1, event1, function (error) {
    if (error) {
        console.log("Saving event1 failed on first peer: " + error.message);
    } else {
        console.log("Saving event1 succeeded on first peer.");
    }
});

allDataPeerClient._put({hostname: "second.peer.com"}, key1, event1, function (error) {
    if (error) {
        console.log("Saving event1 failed on second peer: " + error.message);
    } else {
        console.log("Saving event1 succeeded on second peer.");
    }
});

Test

npm test

Overview

AllDataPeerClient is a Peer HTTP client for AllData. Once configured, it generates _put requests to other peers via HTTP in order to implement various consistency levels for AllData.

Documentation

AllDataClient

Public API

new AllDataPeerClient(options)

  • options: Object
    • method: String (Default: POST) HTTP method.
    • path: String (Default: /) HTTP request path.
    • port: Number (Default: 80) HTTP port of remote server.

Creates a new instance of AllDataPeerClient.

allDataPeerClient._put(options, key, event, callback)

  • options: Object HTTP options specific to this _put.
    • hostname: String HTTP hostname of the AllData peer.
    • method: String (Default: as specified in constructor options.method) HTTP method.
    • path: String (Default: as specified in constructor options.path) HTTP request path.
    • port: Integer (Default: as specified in constructor options.port) HTTP port of remote server.
  • event: Object JavaScript object representing the event to store.
  • callback: Function function (error) {} Callback to call in case of success or failure.

Attempts to store the event with specified key at AllData peer specified in options.hostname via HTTP. callback must be provided and it will be called with an Error instance if an error occurs or with no parameters otherwise.

allDataPeerClient.put({hostname: "first.peer.com"}, key1, event1, function (error) {
    if (error) console.log('put failed: ' + error.message); 
});