FAQ

Q: OMG! Yet another ORM tool? Aren’t there many already?

A: There are quite a few ORM tools for NoSQL databases. Some of them only support a particular datastore while others may support more than one. Kundera currently supports Cassandra, HBase and MongoDB. Idea behind Kundera is to make working with NoSQL databases drop-dead simple and fun. It achieves this objective by:

• Following JPA 2.0 standards
• Leveraging existing libraries like Pelops, MongoDB java driver etc., and builds – on top of them a wrap-around API. This helps developers do away with the unnecessary boiler plate codes, and program a neater, cleaner code that reduces code-complexity and improves quality...and above all, improves productivity.

Q: Why JPA?

A: JPA is very easy to use and most of the people coming from Java EE world are already familiar with it. Another benefit is - code that developers are required to write is the same irrespective of underlying datastore. So switching between datastores is as easy as changing settings in a configuration file. Moreover, Learning JPA-QL is easy which makes it simple to perform operations over NoSQL databases.

Q: I am amazed at the ease of use Kundera provides. But I clueless whether it will give good performance in my enterprise application. Your thoughts?

A: Kundera performance numbers are pretty close to what Pelops, Hector and other similar libraries provide. We tested Kundera with a million record and it worked well. You can test Kundera yourself (and we would love if you share your performance numbers with us). We are in the process of publishing performance numbers.

Home