node remote worker to build distributed master-slave architecture
WebSocket-based remote worker server with health monitoring, message routing, and an opinionated dispatch-first API.
A remote worker system that uses AMQP to coordinate jobs.
An RPC library with strong support for simulating the transfer of functions via postMessage
A simple queue / remote worker server.
Cross origin web worker
No description provided.
Seamless REST/GraphQL API mocking library for browser and Node.js.
A collection of DOM-based utilities for synchronizing elements between JavaScript environments
Utilities for rendering Remote DOM elements using [React](https://reactjs.org/).
Consistent Web Workers in browser and Node.
The worker which is used by the worker-timers package.
Utilities for executing code in Web Workers
A polyfill for the browser APIs used by Remote DOM
A fast, efficient Node.js Worker Thread Pool implementation
Communicate with a Web Worker using Promises, allowing transferList
A little factory function to create a JSON-RPC based Web Worker implementation.
The broker which is used by the worker-timers package.
Temporal.io SDK Worker sub-package
worker loader module for webpack
Distribute processing tasks to child processes with an über-simple API and baked-in durability & custom concurrency options.
Utilities for type-safe Web Worker communication with RPC.
Client Server RPC worker for CSpell.
A simple RPC layer for communicating with web workers and over other transports
Command-line interface for testing internet bandwidth using speedtest.net
A highly parallel Perl 5 interpreter written in Rust
Provides a few rake tasks to run DelayedJob jobs on a remote server over SSH
Mirror a S3 Bucket via command line, with support for remote workers (and scheduling).
Telework is a Resque plugin aimed at controlling Resque workers from the web UI. It makes it easy to manage workers on a complex systems that may include several hosts, different queue(s) and an evolving source code that is deployed several times a day. Beyond starting and stopping workers on remote hosts, the plugin makes it easy to switch between code revisions, gives a partial view of each worker's log (stdout and stderr) and maintains a status of each workers.
Runs 'local' rake commands requested remotely via SNS. For example a worker process can request front end servers to regenerate feeds.
Compatible with Resque 1.x. Use Resque.push if you are using >= 2.x. Resque is great. So is job processing with redis. Our biggest drawback has been that resque requires the class that will be processing a job to be loaded when the job is enqueued. But what happens when the implementing job is defined in a separate application and isn't currently loaded into memory? Enter Resque Remote. Resque Remote's simple goal is to allow you to add a job to a queue with a string identifier for the class rather than the class constant. It is assumed that the worker-side of the equation _will_ have the class in memory and hence will be able to run it no problem. Feedback, comments and questions are welcome at bj [dot] neilsen [at] gmail [dot] com.
Pmrpc (https://github.com/izuzak/pmrpc) is an HTML5 JavaScript library for message passing, remote procedure call and publish-subscribe cross-contex communication in the browser. The library provides a simple API for exposing and calling procedures between browser windows, iframes and web workers, even between different origins. Pmrpc also provides several advanced features: callbacks similar to AJAX calls, ACL-based access control, asynchronous procedure support and fault-tolerance via retries. In case this wasn't clear, pmrpc is not a library for browser-server communication, it is a library for communication within the browser.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.