Your first cloud computing service : PaaS

Introduction

The objective of this project is to propose an extension of the Executor mechanism to outsource its computation on remote resources. Through this interface a java developer should be able to transparently use a either ScheduledThreadPoolExecutor or a ScheduledProActiveExecutor.
You will work in groups of 4 students and the project will proceed as follows:

• Starts on friday february 24th
• Groups registration and usecase proposition by email, with all the members in cc. Deadline : wednesday february 29th
• Deadline for the project submission : monday march 19th

Content of the project deliverable

Your project will have to be submitted as a tar.gz archive named as follow : name1-name2-name3-name4.tar.gz which will deflates as a single directory named name1-name2-name3-name4, and organized as follow :

• name1-name2-name3-name4/src/ containing sources of the project, packaged and documented
• name1-name2-name3-name4/classes/ containing the compiled class files
• name1-name2-name3-name4/lib/ containing your dependencies
• name1-name2-name3-name4/compile/ containing your ant script (responsible for the compilation)
• name1-name2-name3-name4/doc/ containing je javadac and 5-10 pages report which clearly describe your software architecture with entities, communications, etc... You will motivate your design patterns decisions in this report.

Evaluation

The next two classes will be reserved to the project. Your progression will be evaluated. Final version of the project will have to be sent by email at brian.amedro [at] activeeon.com, with all the group members in cc, no later than monday march 19th.

Criterias which will be taken into account for the project evaluation will be :

• Deadline submission
• Design, architecture, distribution
• Robustness
• Code and implementation
• Documentation
• Ease of usage

A project which does not compile will not be evaluated !

Subjet

The java.util.concurrent.ExecutorService interface represents an asynchronous execution mechanism which is capable of executing tasks in the background.
An ExecutorService is thus very similar to a thread pool. In fact, the implementation of ExecutorService present in the java.util.concurrent package is a thread pool implementation.
A nice description is given here: Executor Service

For this project you will create an ExecutorService that instead of relying on a threadpool to execute submitted tasks, send them to a ProActive Scheduler.

As sending tasks to a remote machine can take some time, your interface will have to offer a batching mechanism :

• time-based batching: ex.: do not send more than batch every n seconds
• count-based batching: ex.: send a batch every n submitted tasks

In front of this service, you will have to implement an use case which will submit some tasks on your Executor.

Your are free to propose something for this, but it will have to imply some RESTful communications. For exemple, you can retrieve some data from Google through their APIs and process them thanks to your Executor.