From the website:
Ektorp is a persistence API that uses CouchDB as storage engine. The goal of Ektorp is to combine JPA like functionality with the simplicity and flexibility that CouchDB provides.
Features
Here are some good reasons why you should consider to use Ektorp in your project:
- Rich domain models. With powerful JSON-object mapping provided by Jackson it is easy to create rich domain models.
- Schemaless comfort. As CouchDB is schemaless, the database gets out of the way during application development. With a schemaless database, most adjustments to the database become transparent and automatic.
- Out-of-the-Box CRUD. The generic repository support makes it trivial to create persistence classes.
- Simple and fluent API.
- Spring Support. Ektorp features an optional spring support module.
- Active development. Ektorp is actively developed and has a growing community.
- Choice of abstraction level. From full object-document mapping to raw streams, Ektorp will never stop you if you need to step down an abstraction level.
I am going to be looking at this project more closely but it would be interesting to see a project that said:
Here are some reasons to not use this project and/or things it doesn’t do well…
I can’t recall ever seeing a project that had such a disclaimer.
Not that it would have to be long or detailed, but showing an awareness that whatever the project, it isn’t the universal solution would be nice.