Performance (2.4)

Release: 2.4

Kundera-cassandra

Kundera Performance was compared against Hector / Pelops. Why Hector / Pelops? Kundera is an object-to-datastore maping tool and Hector / Pelops are high level Cassandra clients and therefore this comparison can be argued against but the intent was to calculate the overhead that Kundera is adding while it provides the mapping and other real cool features.

Kundera-hbase

Kundera HBase API's performance was compared against DataNucleus /Native API. Kundera is an JPA compliant object-to-datastore maping tool and intent was to calculate the overhead that Kundera is adding while it provides the mapping and other real cool features.

Kundera-mongo

Kundera mongo API's performance was compared against Spring data / Morphia/Native API. Kundera is an JPA compliant object-to-datastore maping tool and intent was to calculate the overhead that Kundera is adding while it provides the mapping and other real cool features.

Kundera-redis

Kundera Redis API's performance was compared against Jedis java API. Intent was to calculate overhead kundera is imposing over Jedis library which it uses for all operations.

Kundera-neo4j

Kundera neo4j API's performance was compared against Neo4j native java API. Intent was to calculate overhead kundera is imposing over native driver which it uses for all operations.