Hello,

I'm an eager computer science student in my first year of M.Sc. My coding
skills are composed mainly of the Java language family including the
enterprise side of it. My research project is based on the cloud
environment, i am working on a bag of task price optimization application
that allows users to compare cloud providers and automatically chose which
instance is most suitable for their application in particular. Outside of
school i am a java enterprise developer and my projects include creating
and maintainting internal tools for the company i am working for, as well
as writing tests and identifying issues.

I've been speaking with committers from both WHIRR and JAMES in person and
am enlisted to several mailing lists and in this process I've figured out
that i'd like to allocate my time creating a new feature for an opensource
project. I've been playing with WHIRR lately and I definetly see a
posibility through which I can improve the way JAMES is deployed, and make
it deployable on the cloud environment. Thanks to the GSOC last year, JAMES
now has a mailbox implementation on HBASE. This will allow the use of the
features jclouds provides and that are implemented in WHIRR such that
starting a distributed mailing cluster on Amazon or Rackspace would just
take a property file configuration of WHIRR and of JAMES. This would have a
lot of benefits like:

   - easier stress testing
   - automated deployment
   - integration testing
   - benchmarks
   - having just the SMTP server even without mailstore is helpfull,
   providing users with a warranty of server uptime.

Also this aspect would also benefit on working for JIRA issues JAMES-1387
and JAMES-1388. This way JAMES would me more "cloud friendly".

Sincerely,
Mihai Soloi

Reply via email to