Java EE Olio - source code released
By binu on May 21, 2009
The Java EE source code of the Apache incubator project Olio was released two weeks ago. To learn more about the Java EE version of Olio, please check out Kim Lichong's overview blog. Shanti's blog provides an overiew of Olio.
It took a long time for us to get here and there were several detours along the way. This project started off as an extension of the Java EE Blueprints Live project. Thanks to Inderjeet Singh, Mark Basler, Sean Brydon, and Greg Murray (some of them are shown in the picture in the Olio snapshot) for their contributions. Significant portions of the Live code are still in Olio (I am sure there are a few unused artifacts there as well, which we have missed to take out).
We modified the base Live code so that we could analyze the performance and scalability of a Web 2.0 application and added a benchmark driver and harness. The feature set available in Live was used for the 1.0 version of PHP and Rails versions. We went on to modify the Java EE version to incorporate distributed caching using Memcached and some experiments using a distributed file system. At this stage, the plans were changed to release a stripped down version of the code that we had for feature parity with PHP 1.0 (which did not use Memcached). Due to some other priorities, it took us a lot longer to refactor the required changes and get to where we are. So I am extremely glad that we are finally able to release it.
We have a working version of the code available -
Workload Driver: http://svn.apache.org/viewvc/incubator/olio/workload/java
Guide for initial setup and configuration: http://svn.apache.org/viewvc/incubator/olio/docs/java_setup.html?view=log
We are just getting started and there are lots more to be done. Here is a set of tasks that are already identified (I am sure there will be more coming in) -
- Incorporate Memcached or some other distributed caching mechanism.
- Improve the file system interaction. There are parts of the code that assume a local file system. We started on cleaning up this code by defining a file system abstraction layer. But more work is needed to complete the clean up. Once the clean up is complete, look at using distributed file systems (MogileFS, Hadoop).
- Clean up the JSPs to replace JMaki with appropriate JS libraries.
- Implement 'true' REST based services.