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

distributed-wait

v1.0.1

Published

### Supported clients - Redis via redlock

Downloads

4

Readme

Distributed wait

Supported clients

  • Redis via redlock

Why do we need distributed wait ?

Situation: Assume that we have N (in our case 4) containers with shared volume. To perform X task we need Y file. If task producer produces N number of X tasks simultaneously. All worker get X task and to complete it they need Y file, but if all workers download Y file, it will be wasteful and not efficient.

Solution: Only one worker should download Y file at the same time and other worker should wait for it. To perform this we create distributed wait and lock downloading Y file for other workers.

Diagram

Example

// create redis client
const redis = new RedisClient({host: "localhost"});

// create wait client
const redisClient = new RedisWaitClient(new Redlock([redis]));

// Create wait manager
const waitManager = new DistributedWait(redisClient);

const task = async () => {
  await waitManager.waitFor('downloadY', 60000, async () => {
    // only the worker which got the task first downloads file. Other workers just wait and skip downloading phase

    // downloading logic here
  })

  //   
  // complete X task
}

task();