BSON and OSON: documents are designed to be nested, not flat
The article discusses the importance of using BSON and OSON formats for nested documents rather than flat structures. It critiques benchmarks that misuse these formats by comparing relational databases to document databases inappropriately. The author emphasizes that nested documents optimize data organization and querying efficiency.
- ▪BSON and OSON are designed for nested documents, not flat structures.
- ▪Benchmarks that misuse these formats do not reflect real-world implementation trade-offs.
- ▪Nested sub-documents allow for efficient data organization and querying.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 114176) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Franck Pachot Posted on May 30 BSON and OSON: documents are designed to be nested, not flat #document #database #oracle #mongodb I like vendors benchmarks as they are often good illustrations of worst practice. Rather than focusing on real implementation trade-offs, they pick an extreme case that favors their own implementation by chance but is not optimized in the competitor's — because it is simply not how that technology is meant to be used.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
