JPPF 2.2 features
Ease of use
- simple APIs requiring small or no learning curve
- automatic deployment of application code on the grid
- ability to reuse existing or legacy objects without modification
- "happy path" with no additional configuration
- automatic server discovery
- convenient reusable application template to quickly and easily start developing JPPF applications
- straightforward Executor Service interface to the JPPF grid
Self-repair and recovery
- automated node reconnection with failover strategy
- automated client reconnection with failover strategy
- fault tolerance with job requeuing
Job-level SLA
- execution policies enable rule-based node filtering
- maximum number of nodes a job can run on
- job prioritization
- job scheduled start date
- job scheduled expiration date
Management and monitoring
- task-level events
- job-level events
- server performance statistics
- server performance charts
- user-defined charts
- remote server control and monitoring
- remote nodes control and monitoring
- cpu utilization monitoring
- management of load-balancing
- management and monitoring available via APIs and graphical user interface (administration console)
Platform extensibility
- All management beans are pluggable, users can add their own management modules at server or node level
- Startup classes: users can add their own initialization modules at server and node startup
- Security: any data transiting over the network can now be encrypted by the way of user-defined transformations
- Pluggable load-balancing modules allow users to write their own load balancing strategies
- Ability to specify alternative serialization schemes
Performance and resources efficiency
- multiple configurable load-balancing algorithms
- adaptive load-balancing adjusts in real-time to workload changes
- memory-aware servers and nodes with disk overflow
- client-side server connection pools
Dynamic topology scaling
- nodes can be added and removed dynamically from the grid
- servers can be added and removed dynamically from the grid
- servers can work alone or linked in P2P topology with other servers
Third-party connectors
- J2EE connector, JCA 1.5 compliant, deployed as a standard resource adapter
- GigaSpaces XAP connector
- Apache Tomcat connector
Add-ons
- TCP multiplexer, routes JPPF traffic through a single TCP port to work with firewalled environments
Deployment modes
- all components deployable as standalone Java applications
- servers and nodes deployable as Linux/Unix daemons
- servers and nodes deployable as Windows services
- application client deployment as a web, J2EE or GigaSpaces XAP application
Execution modes
- synchronous and asynchronous job submissions
- client can execute in local mode (benefits to systems with many CPUs)
- client can execute in distributed mode (execution delegated to remote nodes)
- client can execute in mixed local/distributed mode with adaptive load-balancing
Full fledged samples
|
