Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "JNoSQL/Artemis"
< JNoSQL
| Line 9: | Line 9: | ||
<br/> | <br/> | ||
| − | To go straight and cover the four NoSQL types, this API has | + | To go straight and cover the four NoSQL types, this API has three domains: |
<br/> | <br/> | ||
| Line 15: | Line 15: | ||
* org.jnosql.artemis.column | * org.jnosql.artemis.column | ||
* org.jnosql.artemis.document | * org.jnosql.artemis.document | ||
| − | |||
* org.jnosql.artemis.key | * org.jnosql.artemis.key | ||
Revision as of 07:36, 4 November 2017
The Eclipse JNoSQL Artemis project is the mapping level, to put it differently, it has the same goals of the either JPA or ORM to NoSQL world, which converts the entity object to Diana model.
This level is in charge to do integration among technologies such as Bean Validation. The Artemis has annotations that make the Java developer life easier. As Diana project, it must be extensible and configurable to keep the diversity on NoSQL database.
To go straight and cover the four NoSQL types, this API has three domains:
- org.jnosql.artemis.column
- org.jnosql.artemis.document
- org.jnosql.artemis.key
The Artemis project
Artemis has three parts:
- Artemis-core: That is the Artemis engine where there are the events, annotations and the Diana integration.
- Artemis-validation: That is the Bean Validation integration as artemis-core plugin.
- Artemis-extension: Like Diana, there is a support for database diversity. This project has extensions to the each database type on the database mapping level.
Links
- More information about the API: https://www.gitbook.com/book/jnosql/jnosql-book/details
- Getting Start with Artemis