incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Incubator Wiki] Update of "JppfProposal" by LaurentCohen
Date Tue, 12 Jan 2010 12:52:36 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Incubator Wiki" for change notification.

The "JppfProposal" page has been changed by LaurentCohen.
http://wiki.apache.org/incubator/JppfProposal?action=diff&rev1=2&rev2=3

--------------------------------------------------

  
  - Comprehensive, easy to use APIs: passing from a single-threaded application model to a
grid-based parallel model can be a daunting task. JPPF facilitates this work by providing
developers with a set of APIs that are simple, can be learned quickly and require a minimal
or no modification to the existing code. 
  
- - No configuration usage: in most environments, JPPF can be deployed without any additional
configuration burden. Nodes and application clients will automatically dicover the servers
on the network. The server will automatically adapt to workload changes and optimize the throughput.
Required code and libraries will be automatically deployed where they are needed. 
+ - No configuration usage: in most environments, JPPF can be deployed without any additional
configuration burden. Nodes and application clients will automatically discover the servers
on the network. The server will automatically adapt to workload changes and optimize the throughput.
Required code and libraries will be automatically deployed where they are needed. 
  
  - Dynamic grid scaling and self-repair: the JPPF grid is fault-tolerant, meaning that the
failure of a node, or even a server, does not compromise the jobs currently executing or scheduled.
In most cases, the performance degradation will be barely noticeable, as JPPF automatically
adapts to topology and workload changes. Furthermore, nodes and servers can be dynamically
started and will be automatically recognized, allowing JPPF to function in "crunch mode".
In addition to this, JPPF components benefit from automatic recovery functionalities. 
  
@@ -21, +21 @@

  
  - Integration with leading application and web servers: by complying with the Java Connector
Architecture 1.5 specification, JPPF integrates seamlessly with and completes the offering
of leading J2EE application servers: Apache Geronimo, JBoss, Glassfish, IBM Websphere, Oracle
Weblogic, Oracle OC4J. JPPF also integrates with GigaSpaces eXtreme Application Platform and
Apache Tomcat web server 
  
- - Extensibility: JPPF offers a number of hooks and extension points that allow users to
extend the framework and adapt it to their own requirements and needs. Such extension mechanisms
are available for custom management and monitoring MBeans, startup classes for grod components,
network data transformation/encryption, additional load-balancing algorithms, alternate object
serialization mechanisms.
+ - Extensibility: JPPF offers a number of hooks and extension points that allow users to
extend the framework and adapt it to their own requirements and needs. Such extension mechanisms
are available for custom management and monitoring MBeans, startup classes for grid components,
network data transformation/encryption, additional load-balancing algorithms, alternate object
serialization mechanisms.
  
  === Background ===
- JPPF is a project being actively developed at SourceForge. It was created to address a class
of problems called "embarassingly parallel", which groups computational problems that can
be decomposed into many smaller sub-problems, that are independant from each other and that
can thus be executed in parallel.
+ JPPF is a project being actively developed at SourceForge. It was created to address a class
of problems called "embarrassingly parallel", which groups computational problems that can
be decomposed into many smaller sub-problems, that are independant from each other and that
can thus be executed in parallel.
  
  === Rationale ===
  Given these last years' emergence of technologies that make commodity hardware, virtualization
and cloud computing available to a fast-growing computing ecosystem, the project answers the
need to execute applications ever faster, with a low entry cost, while at the same time preserving
historical technological investments.
@@ -66, +66 @@

  No one is currently paid to work on JPPF.
  
  === Relationships with Other Apache Products ===
- JPPF is currently refactoring its network communication infrastructure with the help of
Mina (which is how we came to find a sponsor).
+   * JPPF is currently refactoring its network communication infrastructure with the help
of Mina (which is how we came to find a sponsor).
- The project's logging relies entirely on commons-logging and Log4j.
+   * The project's logging relies entirely on commons-logging and Log4j.
- The project also provides connectors for Geronimo and Tomcat.
+   * The project also provides connectors for Geronimo and Tomcat.
- Builds are done with Ant, and we are currently looking at switching to Maven-based builds.
+   * Builds are done with Ant, and we are currently looking at switching to Maven-based builds.
- We foresee that JPPF could be used by many other Apache projects to speed-up the execution
of unit tests by running them in parallel, and to serve as a basis for running distributed
charge and load tests.
+   * We foresee that JPPF could be used by many other Apache projects to speed-up the execution
of unit tests by running them in parallel, and to serve as a basis for running distributed
charge and load tests.
- One of our samples uses Lucene to demonstrate a simple use of a distributed framework for
web search, crawling and indexing
+   * One of our samples uses Lucene to demonstrate a simple use of a distributed framework
for web search, crawling and indexing
  
  === A Excessive Fascination with the Apache Brand ===
  Our main hope in joining the Apache community is that it will help build a strong developers
and committers community around the project, and remove its reliance on a single developer.
We aim at achieving this while attracting new users, in conformance with the Apache spirit
and policies.
@@ -84, +84 @@

    http://sourceforge.net/projects/jppf-project (code repository, bug tracker, features tracker)
  
  == Initial Source ==
- OThe entire code for JPPF is held in a SourceForge CVS repository, and has been so since
the project's inception in April 2005. This entire code base will be donated to Apache.
+ The entire code for JPPF is held in a SourceForge CVS repository, and has been so since
the project's inception in April 2005. This entire code base will be donated to Apache.
  The source code has been licensed under the ASL 2.0 since August 2007. Before that it was
LGPL.
  All artifacts in the trunk and existing branches (1 branch) are now licensed under the ASL
2.0, with corresponding header when applicable.
  

---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org


Mime
View raw message