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

@tasklyhub/scheduler

v1.1.5

Published

schedules tasks

Downloads

172

Readme

Here's a sample README.md file for your npm package @tasklyhub/scheduler. This readme provides a general overview of the package, installation instructions, usage examples, and more.

@tasklyhub/scheduler

TasklyHub Scheduler is an npm package designed to manage and execute scheduled tasks in a Node.js application. It includes worker threads for processing, polling, and task execution, leveraging MongoDB for data persistence and AWS SQS for queue management.

Features

  • Processor Worker: Processes messages from a queue and performs tasks.
  • Polling Worker: Polls the database for tasks that are due and queues them.
  • Task Executor Worker: Executes registered callbacks for queued tasks.
  • Callback Registry: Register and manage callback functions for task execution.
  • MongoDB Integration: Seamless integration with MongoDB for task storage.
  • AWS SQS Integration: Manage tasks in AWS SQS queues.

Installation

You can install the package via npm:

npm install @tasklyhub/scheduler

Usage

Basic Setup

Below are examples of how to set up and start the workers.

Processor Worker

const { MongoDB, Queue, ProcessorWorker } = require("@tasklyhub/scheduler");

const db = new MongoDB("mongodb://localhost:27017", "scheduler", "schedules");

const queue1 = new Queue(
  "http://localhost:9324/000000000000/my-queue",
  "ap-south-1",
  { accessKeyId: "NA", secretAccessKey: "NA" }
);

const processorWorker = new ProcessorWorker(queue1, db);
processorWorker.startWorker();

Polling Worker

const { MongoDB, Queue, PollingWorker } = require("@tasklyhub/scheduler");

const db = new MongoDB("mongodb://localhost:27017", "scheduler", "schedules");

const queue2 = new Queue(
  "http://localhost:9324/000000000000/my-queue-2",
  "ap-south-1",
  { accessKeyId: "NA", secretAccessKey: "NA" }
);

const pollingWorker = new PollingWorker(queue2, db);
pollingWorker.startWorker();

Task Executor Worker

const {
  Queue,
  TaskExecutorWorker,
  CallbackRegistry,
} = require("@tasklyhub/scheduler");

const queue2 = new Queue(
  "http://localhost:9324/000000000000/my-queue-2",
  "ap-south-1",
  { accessKeyId: "NA", secretAccessKey: "NA" }
);

const registry = CallbackRegistry.getInstance();

registry.registerCallback("myCallback", (message) => {
  console.log("Callback executed with message:", message);
});

const taskExecutor = new TaskExecutorWorker(queue2);
taskExecutor.startExecutorWorker();

Running Workers Independently

To leverage multiple cores and run workers independently of your main Express application, use worker threads or child processes.

Using Worker Threads

const { Worker } = require("worker_threads");

function runWorker(workerFile) {
  return new Promise((resolve, reject) => {
    const worker = new Worker(workerFile);
    worker.on("message", resolve);
    worker.on("error", reject);
    worker.on("exit", (code) => {
      if (code !== 0)
        reject(new Error(`Worker stopped with exit code ${code}`));
    });
  });
}

// Start processor worker
runWorker("./processorWorker.js").catch((err) => console.error(err));

// Start polling worker
runWorker("./pollingWorker.js").catch((err) => console.error(err));

// Start task executor worker
runWorker("./taskExecutorWorker.js").catch((err) => console.error(err));

Using Child Processes

const { fork } = require("child_process");

function startWorker(workerFile) {
  const worker = fork(workerFile);

  worker.on("error", (error) => {
    console.error(`Worker ${workerFile} encountered an error:`, error);
  });

  worker.on("exit", (code) => {
    if (code !== 0) {
      console.error(`Worker ${workerFile} stopped with exit code ${code}`);
    }
  });
}

// Start processor worker
startWorker("./processorWorker.js");

// Start polling worker
startWorker("./pollingWorker.js");

// Start task executor worker
startWorker("./taskExecutorWorker.js");

Main Express Application

Ensure your main Express application is in a separate file and does not directly manage the worker processes.

app.js

const express = require("express");
const app = express();

app.get("/", (req, res) => {
  res.send("Hello, World!");
});

app.listen(3000, () => {
  console.log("Server is running on port 3000");
});

Run the main worker manager script to start all workers:

node index.js

Run your Express application separately:

node app.js

Contributing

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

License

This project is licensed under the MIT License. See the LICENSE file for details.


Feel free to modify the content as per your specific package details and usage scenarios.