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

datastore-sequences

v1.0.8

Published

Generate sequential counters for Google Clound Datastore.

Downloads

17

Readme

version NPM Types Last Commit license downloads

datastore-sequences

Generate sequential numbers (auto-increment IDs) in Google Cloud Datastore.

Common wisdom is that you can't or at least shouldn't sequentially number records/rows/entities on Google Cloud Datastore. For background see 1, 2, 3, 4 and 5.

While this is sound advice in most cases, there are situations where you need to have sequential numbered things - e.g. invoice numbers.

datastore-sequences implements a battle tested approach for slow but save sequence numbering. There is a strong guarantee that that no ID will be produced more than once. There is no guarantee that there will never be gaps in the numbering sequence. But this should happen extremely seldom. Thew usage of different Prefixes allows you to have multiple independent sequences.

To use it, you instantiate with a @google-cloud/datastore instance and call allocateId:

import { Datastore } from '@google-cloud/datastore';
import { SequenceNumbering } from 'datastore-sequences';
const numbering = new SequenceNumbering(new Datastore());
const newId1 = await numbering.allocateId();
const newId2 = await numbering.allocateId();
console.log(newId1, newId2)
'1' '2'

This automatically reties getting a new number on datastore congestion and tries to serialize number generation to avoid datastore congestion.

You can give a prefix to get different namespaces:

const newIds = await Promise.all([
  numbering.allocateId('RG'),
  numbering.allocateId('LS'),
  numbering.allocateId('RG'),
  numbering.allocateId('LS')])
console.log(newIds);
['RG1' 'LS1', 'RG2', 'LS2']

You are also encouraged to give a starting value. This is only needed on the first run for a given Prefix:

const newIds = await Promise.all([
  numbering.allocateId('RG', 10000),
  numbering.allocateId('RG'),
]);
console.log(newIds);
[('RG10001', 'RG10002')];

See also