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

djorm-cloud-jobs

v0.2.0-alpha.7

Published

Tiny library that helps you run huge workloads as small distributed jobs in cloud environment

Downloads

158

Readme

djorm-cloud-jobs

Tiny library that helps you run huge workloads as small distributed jobs in cloud environment.

For the moment, only Google Cloud Platform is supported.

Installation

npm install djorm-cloud-jobs

Configuration

Add djorm-cloud-jobs/config to apps djorm config.

const { configure } = require('djorm/config')

configure({
  apps: [
    'djorm-cloud-jobs/config'
  ], 
  jobs: {
    model: 'djorm-cloud-jobs.Job',
    local: process.env.NODE_ENV === 'local'
  }
})

jobs.model

(string, default 'gcpi-models-jobs.Job') name of the model used to store jobs. You can either use the Job model or extend the abstract JobBase model.

jobs.local

(boolean, default false) run the jobs locally (don't use that in production)

Usage

The jobs are expected to be run in Cloud Function environment. So first, you need to create an entrypoint.

const { createSubscription } = require('djorm-cloud-jobs')

module.exports = createSubscription({
  filename: __filename,
  topic: 'job-topic',
  tasks: job => {
    // process job.props
  }
})

The processing stores updates job status based on the outcome of the processing function.

Multiple job types

You can specify that the entrypoint will process multiple different types of Jobs. Good examples are scrapers, so let's scrape some pets API.

const { createSubscription } = require('djorm-cloud-jobs')

const ScrapeTriggers = {
  ownerList: 'load:owner:all', 
  ownerDetail: 'load:owner:detail',
  ownerPetList: 'load:owner:pet:all'
}

module.exports = createSubscription({
  filename: __filename,
  topic: 'job-topic',
  tasks: {
    [ScrapeTriggers.ownerList]: job => {
      // Fetch owner list and trigger details fetch for each owner
      await Promise.all(ownerList.map(owner => 
        job.spawnChild({
          props: {
            owner
          }
        })
      )
    },
    [ScrapeTriggers.ownerDetail]: job => {
      const { owner } = job.props
      // Fetch owner details for a specific owner
      // Store owner details
      // Trigger pets details fetch for each pet
      await Promise.all(owner.pets.map(pet => 
        job.spawnChild({
          props: {
            owner,
            pet
          }
        })
      )

    },
    [ScrapeTriggers.ownerPetList]: job => {
      const { owner, pet } = job.props
      // Now fetch and store the owner's pet's details
    }
  }
})

Job hooks

To make the jobs interact with each other, you can define hooks. Let's consider ScrapeTriggers from previous example. We want to trigger another job when the ScrapeTriggers.ownerList job ends successfully. Please note that it is considered successful only if all the descendants finish with success status.

const { createSubscription } = require('djorm-cloud-jobs')

const LocationTriggers = {
  petLocationHistory: 'load:pet:location-history'
}

module.exports = createSubscription({
  filename: __filename,
  topic: 'job-topic',
  tasks: {
    [ScrapeTriggers.ownerList]: {
      onRequest: job => {
        // Same as above
      },
      onSuccess: job => {
        job.constructor.debounce({
          type: LocationTriggers.fetchPetLocationHistory,
        })
      }
    }
  }
})

Deploying

  1. You need to create all the PubSub topics
  2. You need to create all the Cloud Functions with
  • all the required database env variables
  • entrypoint set to runJob
  1. Potentially other resources