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

bufferedreader

v1.0.4

Published

Buffer responses from asynchronous functions to increase the performance of Node.js applications

Downloads

17

Readme

BufferedReader

BufferedReader

Build Status

NPM

BufferedReader allows you to create a buffer of results from asynchronous requests. This is not to be confused with Node.js' native Buffer type, this is a temporary store that we populate with results of asynchronous requests for the event loop to consume.

The BufferedReader can be used as a drop in replacement for your asynchronous function call, and it will fill a buffer of responses for your request.

Why does this exist?

When modeling some applications, you may find yourself using a waterfall pattern loading in content that you want to perform an action on. Maybe something like this:

async.waterfall([
    function fetchFromSQS...,
    function fetchFromS3...,
    function convertToDocument...,
    function InsertIntoElasticsearch...
])

You may run this waterfall in a loop. The time your event loop spends waiting for the object from S3 and inserting into Elasticsearch could be spent loading the next message from SQS. This module facilitates for that in an easy to consume pattern.

Installation

npm install bufferedreader

Usage

var BufferedReader = require('bufferedreader')

var sqsBuffer = new BufferedReader(10, fetchFromSQS)

sqsBuffer(function fetchedMessage(e, message) {
  console.log(JSON.stringify(message))
})

function fetchFromSQS (cb) {
  // Do all async stuffs...
  return cb(e, message)
}

API

reader = new BufferedReader(length, function populateBuffer)

Creates a new BufferedReader instance.

length is an integer that defines how deep of a buffer the reader should attempt to maintain. For example, if you specify 10 here, the reader will hold at most 10 responses in memory at any one time.

populateBuffer is the function that the reader will use to populate the buffer. It should be in the form of function populateBuffer(cb). The callback provided to your function should be called with the response of your function (irrespective of whether or not it is asynchronous). The values passed to the callback will be passed directly back to you out of the buffer in the same exact order. For example:

cb(`foo`, `bar`, `buzz`)

Will pass foo, bar, buzz back to you in that exact order during the next invocation of reader. It is important to note here that we do not attempt to identify errors. If an error occurs, your invocation of reader should handle that error and move forward with life.

reader(function getResponse)

getResponse is a function that receives the results of the populateBuffer function that the reader was initialized with during construction. This may block while waiting for a result to be placed in the buffer.