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

get-lat-long-queue

v1.0.0

Published

A node js redis package that creates a queue of requests and processes with FIFO principles, spacing requests, and retrieving lattitude and longitude data for a specified address from Nominatim API.

Downloads

3

Readme

get-lat-long

A node js redis package that creates a queue of requests and processes with FIFO principles, spacing requests, and retrieving lattitude and longitude data for a specified address from Nominatim API.

Description

The application works as follows:

  • Request is added to redis queue.
  • Request position and previous request details are retrieved through redis transactions.
  • Race conditions are checked.
  • An appointment slot is given to the request.
  • A distributed lock is acquired at appointment slot and set to time out at specific interval.
  • Request is removed from the queue in the same transaction as new details are set.
  • API call is made

Use of appointment slots improve performance since requests are activated only after the lock expires. However, in case of network latency, if a request is early in it's appointment slot, it will have to wait for the lock to expire. Does ensuring consistent spacing equal to the lock expiry interval.

Getting Started

Dependencies

  • redis

Installing

  • Install with npm i get-lat-long-queue

Executing program

  • Accepts parameters : latLangRedisClient, latLongQueueKey, latLongLockKey, latLongLocalLockKey, latLongProcessingKey, expirationTime // In milliseconds, { id, locationToSearch } // id to identify requests, full address as locationToSearch, displayLogs

  • Example usage in node js redis express application

const express = require('express');
const redis = require('redis');
const getLatLong = require('get-lat-long-queue');

const app = express();
app.use(express.json());

const PORT = process.env.PORT || 3000;

const redisClient = redis.createClient();
redisClient.on('error', (error) => console.error(`Redis Error: ${error}`));
redisClient.connect();


app.use((req, res, next) => {
    req.redisClient = redisClient;
    next();
});

app.post("/getLatLong", async (req, res) => {
    try {
        const { id, locationToSearch } = req.body;

        const result = await getLatLong(
            latLangRedisClient = req.redisClient,
            latLongQueueKey = 'latLongQueueKey',
            latLongLockKey = 'latLongLockKey',
            latLongLocalLockKey = 'latLongLocalLockKey',
            latLongProcessingKey = 'latLongProcessingKey',
            expirationTime = 5000,
            { id, locationToSearch },
            displayLogs = true,
        );
        res.status(200).send({ result });

    } catch (e) {
        console.error(e);
        res.status(500).send('error at main route');
    }
});

app.listen(PORT, () => {
    console.log(`Server running on port: ${PORT}`);
});

Help

Pass displayLogs as true to log the execution flow with times.

displayLogs = true

Author

Kushal Ghimire @KG [email protected]

Version History

  • 0.1
    • Initial Release