Projects / JPPF

JPPF

JPPF enables applications with large processing power requirements to be run on any number of computers, in order to dramatically reduce their processing time. This is done by splitting an application into smaller parts that can be executed simultaneously on different machines.

Tags
Licenses
Operating Systems
Implementation
Translations

RSS Recent releases

  •  02 Apr 2012 15:03

Release Notes: This maintenance release brings important bugfixes

  •  31 Jan 2012 22:50

Release Notes: This release brings incredible improvements in ease of use, stability, reliability and flexibility. The configuration was simplified and improved. Job recovery was improved and job failover was added on the client side. New, fully documented class loading extensions were added. New extension points are now available. The administration console, management, and monitoring features have received new capabilities and improvements. Four full-fledged examples applications were added.

  •  19 Dec 2011 14:54

Release Notes: This maintenance release brings important bugfixes which improve stability and scalability.

  •  14 Nov 2011 23:35

Release Notes: This maintenance release brings important bugfixes, with increased stability and scalability.

Release Notes: This maintenance release brings important bugfixes and minor enhancements, including class loader and serialization bugfixes, along with a port of the J2EE connector to JBoss 7.

RSS Recent comments

28 Dec 2007 03:02 lolocohen

Re: what is its relationship to clustering (e.g. JBoss)?
Hello Jamie,

Thank you for your comments and question.

Indeed, JPPF is not a cluster, but rather a computational grid framework.

The generally agreed upon difference between clusters and grids is that clusters are made of a set of tightly coupled, homogeneous systems (hardware/OS/software) in a single location or complex, whereas grids are loosely coupled, heterogeneous and widely distributed in nature.

In a larger definition, a grid provides access to computational and storage resources across organizational boundaries. In effect, it virtualizes these resources from the user's perspective, as the user doesn't need to know what these resources are made of or where they are located to use them.

A J2EE application server such as JBoss provides clustering capabilities. Its main goal is to serve a large number of relatively short-lived interactions (or transactions) with a large number of users.

On the other hand, a computational grid will serve requests for long-lived intensive computations that can take hours or days or even longer to complete.

In short, frameworks like JBoss and JPPF provide capabilities in different areas, where they do not compete with each other. It is my belief that they instead complement each other. To demonstrate this, we (JPPF team) have developed a connector between JPPF and the major J2EE application servers in the market, including JBoss.

I invite you to find more about it on the JPPF web site at www.jppf.org

I hope this answers your question,

-Laurent

> This project sounds very interesting. My

> question is: what is its relationship

> with clustering setup for example in

> JBoss? Is it a similar thing but in a

> new development? or is it complete a new

> technology?

27 Dec 2007 10:30 jamiescott66

what is its relationship to clustering (e.g. JBoss)?
This project sounds very interesting. My question is: what is its relationship with clustering setup for example in JBoss? Is it a similar thing but in a new development? or is it complete a new technology?

Screenshot

Project Spotlight

SourceSquare

The free open source scanning engine

Screenshot

Project Spotlight

grunt-sizediff

A Grunt task to diff file sizes between a current git branch and a branch/commit.