Displaying 1 to 8 from 8 results

Schedulix - Enterprise Job Scheduling System

  •    Java

Schedulix is the Open Source Enterprise Job Scheduling System, which meets the complex requirements of modern IT process automation. It helps to create Complex workflow, Hierarchical workflow modelling, Workflows can be dynamically submitted or paralleled, Automatic reruns of sub-workflow, Load balancing, Sticky allocations, Time scheduling and lot more.

mongodb-cron - MongoDB collection as crontab

  •    TypeScript

This package offers a simple API for scheduling tasks and running recurring jobs on MongoDB collections. Any collection can be converted into a job queue or crontab list. It uses the officially supported Node.js driver for MongoDB. It's fast, minimizes processing overhead and it uses atomic commands to ensure safe job executions even in cluster environments. This is a light weight open source package for NodeJS written with TypeScript. It's actively maintained, well tested and already used in production environments. The source code is available on GitHub where you can also find our issue tracker.

mongoose-cron - Mongooose collection as crontab

  •    Javascript

MongooseCron is build on top of MongoDB and Mongoose. It offers a simple API for scheduling tasks and running recurring jobs on one or multiple database collections, supporting models and discriminators. It's fast, minimizes processing overhead and it uses atomic commands to ensure safe job executions in cluster environments. Let's say we have a simple application like the one below.




schedule-rs - An in-process scheduler for periodic jobs

  •    Rust

An in-process scheduler for periodic jobs. Schedule lets you run Rust functions on a cron-like schedule. Schedule is primarily distributed under the terms of both the MIT license and the Apache License (Version 2.0).

factotum - A system to programmatically run data pipelines

  •    Rust

A dag running tool designed for efficiently running complex jobs with non-trivial dependency trees. Specifying variables in the job file can be done using --env JSON (or -e JSON). The JSON here is free-form and needs to correspond to the placeholders you've set in your job.