Search Results for "java ssh client"

JPPF makes it easy to parallelize computationally intensive tasks and execute them on a Grid.

The Orchestrator server is responsible for distribution and launch of simple apply/rollback shell scripts in a particular order across multiple servers . If for any reason deployment is failing at a particular stage the process will stop and you can rollback any changes done until then. In case you want to deploy your code or just call your preferred DSC client to apply the configuration locally the Orchestrator can be a handy tool. The operation can be started manually or scheduled,...

A Java servlet filter which moves session storage out of the java application container, allowing to scale easily by adding more servers, without using a cluster nor changing the code. Session data can be stored into a cookie, memcached, a DB ...

Cluster101 allows you to run software on many hosts and perform a simple task scheduling. No need to install any software on the hosts (it just runs tasks via ssh). It is typically used for running scientific applications on University campuses.

A client understands only one IP address to avail various services which can be hosted in different servers.

The primary goal of the JES is to develop Distributed Configuration Service for client/server,clusters,grids,agent based architectures.

Alternative implementation of Spring framework remoting subsystem that supports different schemes of remote communication between client and server (1-1, 1-many, dynamic services discovering).

A small client/server/node application written in java for distributed computing, or clustering. you write your programs to use this system, you create an object with a meathod to run and send it to the server that assign it a node.

Java package containing architecture to distribute CPU intensive processing tasks across the internet. A generic client will be capable of running any task the server provides it, automatically updating the code it runs.

A Java client for the memcached protocol with a configurable client-side in-process memory cache supporting replacement/eviction strategies (least-recently-used, least-frequently-used, first-in-first-out) designed to provide extremely low-latency lookup.