DODB
This commit is contained in:
parent
03da23e8e2
commit
6f170b60ab
@ -89,17 +89,32 @@ A lot of designs won't be mentioned here.
|
||||
The actual history of databases is often quite unclear since the categories of databases are sometimes vague, underspecified.
|
||||
As mentioned, SQL is not a silver bullet and a lot of developers shifted towards other solutions, that's the important part.
|
||||
.FOOTNOTE2
|
||||
.TBD
|
||||
The
|
||||
Document-oriented databases are key-value stores.
|
||||
Furthermore, metadata is extracted for further optimization.
|
||||
|
||||
Contrary to SQL, DODB has a very narrow scope: to provide a library enabling to store, retrieve, modify and delete data to the application.
|
||||
Thus, DODB doesn't provide an interactive shell, no request language to perform arbitrary operations on the database, etc.
|
||||
The NoSQL movement started because the stated goals of many actors from the early Web boom were different from SQL.
|
||||
The need for very fast operations far exceeded what was practical at the moment with SQL.
|
||||
This led to the use of more basic methods to manage data such as
|
||||
.I "key-value stores" ,
|
||||
which simply associate a value with an
|
||||
.I index
|
||||
for fast retrieval.
|
||||
In this case, there is no need for the database to have
|
||||
.I tables ,
|
||||
data may be untyped, the entries may even have different attributes.
|
||||
Since homogeneity is not necessary anymore, databases have fewer (or different) constraints.
|
||||
Document-oriented databases are a sub-class of key-value stores, where metadata can be extracted from the entries for further optimizations.
|
||||
And that's exactly what is being done in Document Oriented DataBase (DODB).
|
||||
|
||||
Contrary to SQL, DODB has a very narrow scope: to provide a library enabling to store, retrieve, modify and delete data.
|
||||
In this way, DODB transforms any application in a database manager.
|
||||
DODB doesn't provide an interactive shell, there is no request language to perform arbitrary operations on the database, no statistical optimizations of the requests based on query frequencies, etc.
|
||||
Instead, DODB reduces the complexity of the infrastructure, stores data in plain files and enables simple manual scripting with widespread unix tools.
|
||||
Simplicity is key.
|
||||
.
|
||||
.SECTION Basic usage
|
||||
.
|
||||
.SECTION A few more options
|
||||
.
|
||||
.SECTION Limits of DODB
|
||||
.
|
||||
.SECTION Experimental scenario
|
||||
.LP
|
||||
The following experiment shows the performance of DODB based on quering durations.
|
||||
|
@ -1,7 +1,7 @@
|
||||
.\" .RP = report document
|
||||
.nr PO 0.5i \" page offset default 1i
|
||||
.nr LL 7.0i \" line length default 6i
|
||||
.nr FM 0.8i \" page foot margin default 1i
|
||||
.nr FM 0.3i \" page foot margin default 1i
|
||||
.nr DI 0
|
||||
.nr FF 3 \" footnotes' type: numbered, with point, indented
|
||||
.
|
||||
|
Loading…
Reference in New Issue
Block a user