Baguette/dodb.cr
3
0
Fork 1
Code Issues Pull Requests Releases Wiki Activity

DODB

Browse Source
This commit is contained in:
Philippe PITTOLI 2024-05-14 16:19:46 +02:00
parent 03da23e8e2
commit 6f170b60ab
2 changed files with 23 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

29
graphs/graphs.ms
View File

@ -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. 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. As mentioned, SQL is not a silver bullet and a lot of developers shifted towards other solutions, that's the important part.
.FOOTNOTE2 .FOOTNOTE2
.TBD The NoSQL movement started because the stated goals of many actors from the early Web boom were different from SQL.
The The need for very fast operations far exceeded what was practical at the moment with SQL.
Document-oriented databases are key-value stores. This led to the use of more basic methods to manage data such as
Furthermore, metadata is extracted for further optimization. .I "key-value stores" ,
which simply associate a value with an
Contrary to SQL, DODB has a very narrow scope: to provide a library enabling to store, retrieve, modify and delete data to the application. .I index
Thus, DODB doesn't provide an interactive shell, no request language to perform arbitrary operations on the database, etc. 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 Basic usage
.
.SECTION A few more options .SECTION A few more options
.
.SECTION Limits of DODB .SECTION Limits of DODB
.
.SECTION Experimental scenario .SECTION Experimental scenario
.LP .LP
The following experiment shows the performance of DODB based on quering durations. The following experiment shows the performance of DODB based on quering durations.

2
graphs/macros.roff
View File

@ -1,7 +1,7 @@
.\" .RP = report document .\" .RP = report document
.nr PO 0.5i \" page offset default 1i .nr PO 0.5i \" page offset default 1i
.nr LL 7.0i \" line length default 6i .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 DI 0
.nr FF 3 \" footnotes' type: numbered, with point, indented .nr FF 3 \" footnotes' type: numbered, with point, indented
. .