Icontem

Node.js Background Jobs: Run background jobs using Node.js modules

Recommend this page to a friend!
  Info   View files Documentation   View files View files (13)   DownloadInstall with Composer Download .zip   Reputation   Support forum   Blog    
Last Updated Ratings Unique User Downloads Download Rankings
2014-08-04 (5 years ago) RSS 2.0 feedNot yet rated by the usersTotal: 124 All time: 374 This week: 9Up
Version License JavaScript version Categories
background-jobs 1.0BSD License0.10.15Networking, Node.js
Description Author

This package can be used to run background jobs using Node.js modules.

It implements a service that can take UDP or TCP socket connections to receive requests to execute jobs implemented by modules.

Multiple jobs may be queued by the service. It can either wait for a job to finish and return its results or just query the status of execution of the job.

Innovation Award
JavaScript Programming Innovation award nominee
August 2014
Number 4
Some applications need to run certain types of jobs regularly or on demand. Those jobs may take a certain time to complete.

This package implements a Node.js based server solution to run multiple jobs in the background by taking requests via network connections.

Manuel Lemos
  Performance   Level  
Name: Thomas Björk <contact>
Classes: 5 packages by
Country: Sweden Sweden
Age: 51
All time rank: 391 in Sweden Sweden
Week rank: 21 Up1 in Sweden Sweden Equal
Innovation award
Innovation award
Nominee: 4x

Details

BackgroundService

BackgroundService is a modular system that enables a primary system to unload some of the more heavy duties to this background system.

By using the tcp service the BackgroundService also allows the calling system to expand it's functionality.

The service was originally created to be used as a subssytem to a CMS to handle logging and error reporting.

Switches

There are some switches that can be used when starting the service.

-v

Use verbose output. This is useful for debugging purpose.

-E

Catch all error not handled anywhere else in the global error handler.

-e

Don't catch all errors in the global error handler. By using this switch the service doesn't even create the global error handler.

This is the default behaviour.

-EE

Be setting -EE the output from the global error handler is sent to console.error.

This requires the -E switch to enable the global error handler.

Modules

The functionality of the BackgrundService is more or less based upon modules.

Exports

When i modules is loaded there should be two functions exported, UExecute and TExecute-

UExecute = function(parts)

UExecute is called from the datagram service.

The result of the function should be returned from this function with the return statement. However the returned data will not be used.

The intention is to run services without interaction with the client. Just start the job and then forget about it. This is the real idea behind the project BackgroundService even though it might seem as the focus lies on the TExecute functionality.

Argument - parts

The parts argument is divided into two parts. The first part is the modules name and the second part is the data (most often a string) intended for the module.

The parts argument is an array where the module name resides in parts[0] and the data can be found in parts[1].

TExecute = function(parts, client)

TExecute is called from the tcp service.

This function doesn't have to return anything. The result should instead be written to the client.write() function.

Argument - parts

The parts argument is divided into two parts. The first part is the modules name and the second part is the data (most often a string) intended for the module.

The parts argument is an array where the module name resides in parts[0] and the data can be found in parts[1].

Argument - client

The client argument is an object containing the client socket. Normally the result will be written to the client.write function.

Unload = function()

This is a non-mandatory function. It is called (if it exists) when the modules file has been changed. This is a part of the AutoReloadModule function that automatically checks everi loaded module each 10 seconds. If the loaded modules main file has an altered mtime (files modification time) then it is automatically unloaded. If the module has done call to require these should be unloaded manually by the module.

exports.Unload = function() {
  var name = require.resolve('module-name-loaded-by-the-module');
  delete require.cache[name];
}

Calling conventions

A call to the BackgroundService should contain a string.

The initial content of the string up until the presence of a colon (*) is considered the module name. If the colon is omitted then the entire string is considered a module name.

The module name is cleaned so that it only contains the letters a-z, A-Z and the digits 0-9 as well as hyphens (-) and underscores (_). All other charactes are considered illegal and will be removed.

All modules reside in a subfolder called modules and they should have a file extension of .js to be detected by the service.

Example modules

There are a few services included for demo purposes.

coffee.js

Uses the node module coffee-script to compile the content as CoffeeScript.

This module is intended for tcp services only.

fail.js

A simple module without exports to test the error handling of the service.

jade.js

Uses the node module jade to compile templates in jade to html.

This module is intended for tcp services only.

less.js

Uses the node module less to compile less scripts into css.

This module is intended for tcp services only.

roole.js

Uses the node modules roole-parser and roole-compiler to compile roole scripts into css.

This module is intended for tcp services only.

sass.js

Uses the node module node-sass to compile sass/scss scripts into css.

This module is intended for tcp services only.

at the time of writing this there are some issues with node-sass that might make it fail to install

test.js

A simple test module that returns the string Test.

typescript.js

This module uses a command line interaction to compile typescript scripts into javascript.

This module is intended for tcp services only.

Queue

The tcp service can be called with a prefix queue: followed by the action and the normal argument.

This will create a "background" job that can be referred to with an id.

queue:add:

The prefix queue:add: will add the request as a background job and return an id prefixed with id:

queue:get:

The request should be in the form queue:get:id:<<id>> where <<id>> is the jobs id.

The request waits until the job has finnished and then returns the result as if the request was made with a direct call.

queue:check:

This is a status check. The request should have the form queue:check:id:<<id>> where <<id>> is the jobs id.

The request returns the current status if the job. 0 if it hasn't been started, 1 if it has started and 2 if it is done.

Examples in PHP

This simple example tries to send the session-id to a fictive module called registersession.

$fp = @stream_socket_client('udp://127.0.0.1:12341', $errno, $errstr);
if($fp) {
  @socket_set_timeout($fp, 0, 50);
  if($data !== null) {
    @fwrite($fp, 'registersession:'.session_id());
  }
  @fclose($fp);
}

This simple example tries to compile a less script to css. In the first step it attempts to connect to the background service at port 12341 on localhost (127.0.0.1). If this fails it tries to use the command line to interact.

function CompileLESS($code) {
  $fp = @fsockopen('tcp://127.0.0.1:12341');
  if($fp) {
    fputs($fp, 'less:'.utf8_encode($code));
    $result = '';
    while(!feof($fp)) {
      $result .= @fgets($fp, 1024);
      break;
    }
    if(!preg_match('/^[45][0-9]{2}\:/Us', ltrim($result))) {
      return utf8_decode($result);
    }
    return null;
  }
  $tempfile = sys_get_temp_dir().'/'.uniqid('less');
  $infile = $tempfile.'.less';
  $outfile = $tempfile.'.css';
  system('lessc '.$infile.' > '.$outfile);
  unlink($infile);
  if(file_exists($outfile)) {
    $code = file_get_contents($outfile);
    unlink($outfile);
    return $code;
  }
  return null;
}
  Files folder image Files  
File Role Description
Files folder imagemodules (8 files)
Accessible without login Plain text file LICENSE Lic. License text
Accessible without login Plain text file package.json Data Auxiliary data
Accessible without login Plain text file README.md Doc. Documentation
Accessible without login Plain text file service.config Conf. Auxiliary data
Plain text file service.js Class Class source

  Files folder image Files  /  modules  
File Role Description
  Accessible without login Plain text file coffee.js Example Example script
  Accessible without login Plain text file fail.js Example Module to test failure
  Accessible without login Plain text file jade.js Example Example script
  Accessible without login Plain text file less.js Example Example script
  Accessible without login Plain text file roole.js Example Example script
  Accessible without login Plain text file sass.js Example Example script
  Accessible without login Plain text file test.js Example Example script
  Accessible without login Plain text file typescript.js Example Example script

 Version Control Unique User Downloads Download Rankings  
 92%
Total:124
This week:0
All time:374
This week:9Up