Skip to Navigation
NoSQL is not hard, it’s different. And to show that, RavenDB and Alex Klaus kick off a new series of articles dedicated to building enterprise applications leveraging the .NET Core + RavenDB bundle.
Description of the case study, high-level domain model and architecture design.
NoSQL Data Model. Practical modelling of the same database for a traditional SQL and a NoSQL. Comparison of the two approaches and their alignment with the DDD (Domain Driven Design).
How to pass document IDs in the URL, mask the ID, drop the prefix, expose nested references, store processed IDs in the DB records, customise the ID, GUID, customise the ID convention, collect name, artificial ID.
The power of dynamic fields for indexing dictionaries and nested collections in RavenDB.
Designing ‘one-to-many’ and ‘many-to-many’ relationships to reduce read operations on querying the data. Based on a YABT example of relationships between Users, Backlog Items, and Comments. Each approach was considered from various angles taking into account the performance, operational costs, time/costs of development and maintenance.
See how multi-tenant database can be arranged in NoSQL in general and in RavenDB in particular – YABT project.
Dear User,
By browsing on this website you are agreeing to our ‘Terms & Conditions’ and the ‘Privacy Policy’ in regards to your rights and personal data handling.
