Skip to main content

JPPF: an Java Open Source solution for parallel processing



JPPF (http://www.jppf.org/) is a Java framework which can help to implement and run a parallel Java program. It allows a Java application to run independent parts of it on different machines in parallel in order to dramatically reduce their processing time. It is useful to split a computing-intensive Java application into several mostly independent parts (which are typically called tasks).
JPPF is Open Source and released under the Apache license 2.0.
These are the main features of this framework:
  • Allows a grid (a server, to which any number of execution nodes are attached.) to be up and running in minutes.
  • Provides a simple programming model that abstracts the complexity of distributed and parallel processing .
  • It's an highly scalable (from small to large networks) and distributed framework for the parallel execution of cpu intensive tasks.
  • Provides seamless integration with the most popular J2EE application servers (IBM WebSphere, JBoss, WebLogic, etc.).  
  • Comes with fault-tolerance and self-repair capabilities to ensure service and reliability.
  • It's cross-platform (of course, it's pure Java).
  • Provides both graphical and programmatic tools for fine-grained monitoring and administration.
The figure below (taken from the official website) shows a typical JPPF topology:


In the real world there are a lot of examples of application of parallel processing (scientific research, 3D rendering, data mining, AI, etc.) and I think that it could be preferred to concurrency in other boundaries when you have good hardware availability.
I discovered this framework more than one year ago and started to make a proof of concept afterhours in order to understand possible benefits applying it to uncommon applications. As soon as possible I will share the results and my opinion on this.

Comments

Post a Comment

Popular posts from this blog

Streamsets Data Collector log shipping and analysis using ElasticSearch, Kibana and... the Streamsets Data Collector

One common use case scenario for the Streamsets Data Collector (SDC) is the log shipping to some system, like ElasticSearch, for real-time analysis. To build a pipeline for this particular purpose in SDC is really simple and fast and doesn't require coding at all. For this quick tutorial I will use the SDC logs as example. The log data will be shipped to Elasticsearch and then visualized through a Kibana dashboard. Basic knowledge of SDC, Elasticsearch and Kibana is required for a better understanding of this post. These are the releases I am referring to for each system involved in this tutorial: JDK 8 Streamsets Data Collector 1.4.0 ElasticSearch 2.3.3 Kibana 4.5.1 Elasticsearch and Kibana installation You should have your Elasticsearch cluster installed and configured and a Kibana instance pointing to that cluster in order to go on with this tutorial. Please refer to the official documentation for these two products in order to complete their installation (if you do

Exporting InfluxDB data to a CVS file

Sometimes you would need to export a sample of the data from an InfluxDB table to a CSV file (for example to allow a data scientist to do some offline analysis using a tool like Jupyter, Zeppelin or Spark Notebook). It is possible to perform this operation through the influx command line client. This is the general syntax: sudo /usr/bin/influx -database '<database_name>' -host '<hostname>' -username '<username>'  -password '<password>' -execute 'select_statement' -format '<format>' > <file_path>/<file_name>.csv where the format could be csv , json or column . Example: sudo /usr/bin/influx -database 'telegraf' -host 'localhost' -username 'admin'  -password '123456789' -execute 'select * from mem' -format 'csv' > /home/googlielmo/influxdb-export/mem-export.csv

Using Rapids cuDF in a Colab notebook

During last Spark+AI Summit Europe 2019 I had a chance to attend a talk from Miguel Martinez  who was presenting Rapids , the new Open Source framework from NVIDIA for GPU accelerated end-to-end Data Science and Analytics. Fig. 1 - Overview of the Rapids eco-system Rapids is a suite of Open Source libraries: cuDF cuML cuGraph cuXFilter I enjoied the presentation and liked the idea of this initiative, so I wanted to start playing with the Rapids libraries in Python on Colab , starting from cuDF, but the first attempt came with an issue that I eventually solved. So in this post I am going to share how I fixed it, with the hope it would be useful to someone else running into the same blocker. I am assuming here you are already familiar with Google Colab. I am using Python 3.x as Python 2 isn't supported by Rapids. Once you have created a new notebook in Colab, you need to check if the runtime for it is set to use Python 3 and uses a GPU as hardware accelerator. You