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

@gromo-fintech/nestjs-central-locking

v0.0.4

Published

A NestJS library for distributed locking using Redlock and Redis.

Downloads

18

Readme

Central Locking

A NestJS library for distributed locking using Redis. This package helps you manage distributed locks in a NestJS application, ensuring that only one instance of a process runs at a time.

Table of Contents

Installation

To install the package, use npm or yarn:

npm install @gromo-fintech/central-locking-service

or

yarn add @gromo-fintech/central-locking-service

Usage

Setup

First, import the LockingModule into your NestJS application module:

import { Module } from '@nestjs/common';
import { LockingModule } from 'central-locking-service';

@Module({
  imports: [LockingModule],
})
export class AppModule {}

Using the Locking Decorator

You can use the CentralLock decorator to ensure a method acquires a lock before execution. This is useful for scenarios where only one instance of a method should run at a time across distributed systems.

import { CentralLock, LockingService } from 'central-locking-service';

export class SomeService {
  constructor(private lockingService: LockingService) {}

  @CentralLock({
    lockKey: 'unique-lock-key',
    lockDuration: 10000,
    shouldReleaseAfterExecution: true,
    shouldThrowErrorIfUnableToAcquireLock: true,
  })
  async handleTask() {
    console.log('Task is being handled.');
    // Your business logic here
  }
}

API

CentralLock Decorator

The CentralLock decorator is used to manage distributed locks on methods.

Options:

  • lockKey (string): The key to identify the lock.
  • lockDuration (number): The duration (in milliseconds) for which the lock should be held.
  • shouldReleaseAfterExecution (boolean): Whether to release the lock after method execution.
  • shouldThrowErrorIfUnableToAcquireLock (boolean): Whether to throw an error if unable to acquire the lock.

LockingService

The LockingService provides methods to acquire and release locks.

Methods:

  • acquireLock(key: string, duration: number): Promise<void>: Acquires a lock for a specific duration.
  • releaseLock(key: string): Promise<void>: Releases the lock for the specified key.

Contributing

Contributions are welcome! Please submit a pull request or open an issue to discuss any changes or improvements.

  1. Fork the repository.
  2. Create your feature branch: git checkout -b feature/your-feature
  3. Commit your changes: git commit -m 'Add some feature'
  4. Push to the branch: git push origin feature/your-feature
  5. Open a pull request.

Author

Saket Anand

Lead Engineer
Saket Anand is the lead engineer behind the @gromo-fintech/nestjs-central-locking. With a deep focus on leveraging Redis, his work has been central to the efficient central locking provided by this library.

License

MIT licensed