Mailing-List: contact user-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@accumulo.apache.org
Message-ID: <55B91541.4030701@gmail.com>
Date: Wed, 29 Jul 2015 14:02:41 -0400
From: Josh Elser <josh.elser@gmail.com>
User-Agent: Postbox 3.0.11 (Macintosh/20140602)
MIME-Version: 1.0
To: user@accumulo.apache.org
Subject: Re: Question regarding java being the choice for accumulo
References: 
 <CADXX17MbWbiJ=G4wBPXpsQBtfHsQszmNjCgjbamTPN-Hw9NZhg@mail.gmail.com>
In-Reply-To: 
 <CADXX17MbWbiJ=G4wBPXpsQBtfHsQszmNjCgjbamTPN-Hw9NZhg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Short answer is probably because Hadoop was written in Java :smile:

Some general points brought up by Doug Cutting for choosing Java for 
Hadoop (back in the Nutch days) are probably applicable here too

* Java's code is portable and platform independent which is based on 
Write Once Run Anywhere.
* Java is fairly simple language to learn to develop a complex and large 
project. Java project are easy to manage.
* Java has a huge collection of open source libraries than any other 
language.
* Java programs crashes less catastrophically and it is easier to debug 
an issue in Java then C or C++.
* Garbage Collection techniques is easier to reuse or extend to a 
project need in Java.

That's my take on it, anyways.

vaibhav thapliyal wrote:
> Hello everyone,
>
> I was wondering why did the developers chose java for writing accumulo.
> What advantage it has over using any other language say C++(in which
> another popular nosql database MongoDB is written) in context of accumulo?
>
> Thanks
> Vaibhav
>