-
Notifications
You must be signed in to change notification settings - Fork 25
/
package-info.java
50 lines (49 loc) · 2.84 KB
/
package-info.java
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
/*
* Copyright (c) 2022 Contributors to the Eclipse Foundation
*
* This program and the accompanying materials are made available under the
* terms of the Eclipse Public License v. 2.0 which is available at
* http://www.eclipse.org/legal/epl-2.0.
*
* This Source Code may also be made available under the following Secondary
* Licenses when the conditions for such availability set forth in the Eclipse
* Public License v. 2.0 are satisfied: GNU General Public License, version 2
* with the GNU Classpath Exception which is available at
* https://www.gnu.org/software/classpath/license.html.
*
* SPDX-License-Identifier: EPL-2.0 OR GPL-2.0 WITH Classpath-exception-2.0
*/
/**
* Defines the API to Document Collection in mapping level. This API going to focus in domain, in other words, ubiquitous language.
* <p>
* A document-oriented database, or document store, is a computer program designed for storing, retrieving, and managing document-oriented information,
* also known as semi-structured data. Document-oriented databases are one of the main categories of NoSQL databases,
* and the popularity of the term "document-oriented database" has grown with the use of the term NoSQL itself.
* </p>
* <p>
* XML databases are a subclass of document-oriented databases that are optimized to work with XML documents.
* </p>
* <p>
* Graph databases are similar, but add another layer, the relationship, which allows them to link documents for rapid traversal.
* </p>
* <p>
* Document-oriented databases are inherently a subclass of the key-value store, another NoSQL database concept.
* </p>
* <p>
* The difference lies in the way the data is processed; in a key-value store the data is considered to be inherently opaque to the database, whereas a document-oriented system
* relies on internal structure in the document in order to extract metadata that the database engine uses for further optimization.
* </p>
* <p>
* Although the difference is often moot due to tools in the systems, conceptually the document-store is designed to offer a richer experience with modern programming techniques.
* </p>
* <p>
* Document databases contrast strongly with the traditional relational database (RDB).
* Relational databases generally store data in separate tables that are defined by the programmer, and a single object may be spread across several tables.
* Document databases store all information for a given object in a single instance in the database, and every stored
* object can be different from every other.
* This makes mapping objects into the database a simple task, normally eliminating anything similar to an
* object-relational mapping. This makes document stores attractive
* for programming web applications, which are subject to continual change in place, and where speed of deployment is an important issue.
* </p>
*/
package jakarta.nosql.document;