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

kvsync

v1.0.23

Published

Synchronization between two abstract key-value storages

Downloads

29

Readme

Algorithm

1. Acquire locks

Get lock files from both source and target storages and ensure that the objects either do not exist or exist but have passed expiration period. If both lock objects meet that conditions - new lock objects are put to the storage with appropriate metadata, including expiration.

2. Commit changes

Writing changes passed as the input to source index.

3. Pull indices

Reading index files from both source and target storages. Process is optimized to read as less data as possible. Only indices which represent the delta between source and target are pulled - process stops as soon as the first common change is found in both storages.

4. Calculate delta

Using change log obtained from index files, determine the list of changes which are missing in the opposite storage (exist in source but missing in target, exist in target but missing in storage).

5. Commit deltas

Writing index files with the changes from the opposite storage which are missing in the current one (from source to target and from tarted to source).

6. Push deltas

Applying change log which represents delta between source and target to both storages.

7. Release locks

Delete lock files created at the beginning of the process. Occurs also in case of an error.