tag:blogger.com,1999:blog-16764551.post1100792684697836945..comments2009-03-01T12:20:12.015-08:00Deepal Jayasinghehttp://www.blogger.com/profile/00591507526772769955noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-16764551.post-61615339704696682492009-03-01T12:20:00.000-08:002009-03-01T12:20:00.000-08:00Deepal,<BR/><BR/>Eucalyptus project uses both Axis2/Java and Axis2/C project. They also use Rampart for ws-security stuff. I was very happy to see Rich Wolski, director of that project, endorsing Axis2 project during his keynote in eScience 2008. <BR/><BR/>I think recommending Eucalyptus might not be the best to anyone who wants to get cloud experience, with minimal trouble. At least for the time being they have limited resources and you have to manually get approval to use it. <BR/>For some one to take a quick look at and experience cloud, I think Amazon EC2 is not that expensive. Also Eucalyptus still doesn't have a counterpart for S3 and EBS but they will do it soon. <BR/><BR/>From scientific research point-of-view, it doesn't matter which one we use. Eucalyptus uses same Amazon APIs so we should be able to do a Turing test for Eucalyptus and EC2 infrastructures, at least theoretically. But Eucalyptus will provider (at least i hope) more instrumentation than Amazon for obvious reasons.<BR/>For your information, I implemented clients to talk to Amazon EC2 and S3 API. Azeez had already done an EC2 implementation using Axis2, and I improved it and also implemented S3 to better support my scenarios. As you know the clients Amazon is distributing are based on XFire. But I believe using Axis2 clients will provide more flexibility and performance at least from the scientific point-of-view.Eran Chinthakahttp://www.blogger.com/profile/10659422557269526208noreply@blogger.com