Note that there are some explanatory texts on larger screens.

plurals
  1. POHigh Level Java Client selection for Apache Cassandra
    text
    copied!<p>There are four high level APIs to access Cassandra and I do not have time to try them all. So I hoped to find somebody who could help me to choose the proper one.</p> <p>I'll try to write down my findings about them:</p> <h2>Datanucleus-Cassandra-Plugin</h2> <p>pros:</p> <ul> <li>supports JPA1, JPA2, JDO1 - JDO3 - as I read in a review, JDO scales better than Hibernate with JPA </li> <li>all the pros as mentioned in kundera?</li> </ul> <p>cons:</p> <ul> <li>no exeirience with JDO up to now (relevant only for me of course ;)</li> <li>documentation not found!</li> </ul> <h2>kundera</h2> <p>pros:</p> <ul> <li>JPA 1.0 annotations with all advantages (standard conform, no boilerplate code, ...)</li> <li>promise for following features in near future: JPA listeners, @PrePersist @PostPersist etc. - Relationships, @OneToMany, @ManyToMany etc. - Transactional support, @Transactional</li> </ul> <p>cons:</p> <ul> <li>early development stage of the plugin?</li> <li>bugs?</li> <li>no possibillity to fix problems in the JDO / JPA framework?</li> </ul> <h2>s7 pelops</h2> <p>pros:</p> <ul> <li>pure java api --> finer control over persistence?</li> </ul> <p>cons:</p> <ul> <li>pure java api --> boilerplate code</li> </ul> <h2>hector 0.7</h2> <p>pros:</p> <ul> <li>mavenized</li> <li>spring integration --> dependency injection</li> <li>pure java api --> finer control over persistence?</li> <li>jmx monitoring?</li> <li>managing of nodes seems to be easy and flexible</li> </ul> <p>cons:</p> <ul> <li>pure java api (no annotations) --> boiler plate code</li> </ul> <h2>Conclusion so far</h2> <p>As I am confident with RDMS, Hibernate, JPA, Spring and not so up to date anymore with EJB, my first impression was, to go for kundera would have been the right choice. But after reading some posts regarding JPO, DataNucleus, I am not sure anymore. As the learning curve should be steep (also for expirienced JPA developers?) for DataNucleus, I am not sure, whether I should go for it.</p> <p>My major concern is the status of the plugin. Also the forum support/help for JDO and Datanucleus-Cassandra-Plugin, as it is not as wide spread, as far as I understood.</p> <p>Is anybody out there, who has experience, with some of the framworks already and can give me a hint? Maybe a mixed strategy would make sense as well. In cases (if they exist) JDO is not flexible/sufficient/whatever enough for my needs, to fall back to one of the easier APIs of pelops or hector? Is this possible? Is there an approach like in JPA to get an sql connection and fetch/put data?</p> <hr> <p>After reading a bit on, I found following additional information:</p> <blockquote> <p>Datanucleus-Cassandra-Plugin is based on the pelops, which also can be accessed for more flexibility, more performance (?), which should be used on the column families with a lot of data, JDO/JPA access should be only used on "administrative" data, where performance is not so important and data amount is not overwhelming.</p> </blockquote> <p>Which still leaves the question open to start with hector or pelops.</p> <p>pelops for it's later Datanucleus-Cassandra-Plugin extensibility, or hector for it's more sufficient support on node hanldling.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload