RavenDB: All content tagged as RavenDB in NoSQL databases and polyglot persistence
What I’ve noticed in these posts:
- RavenDB requires defining the actual shard servers in your sharding implementation (i.e. in your source code)
when performing writes there’re a bunch of round trips (for id generation)
Original title and link: RavenDB Sharding ( ©myNoSQL)
Staying with data modeling, but moving to the world of document databases, Ayende has two great posts about modeling an auction system: part 1 and part 2. They are great not only because it’s not the Human-has-Bird-and-Cat-and-Dogs example, but also because he looks at different sets of requirements and offers different solutions.
That is one model for an Auction site, but another one would be a much stronger scenario, where you can’t just accept any Bid. It might be a system where you are charged per bid, so accepting a known invalid bid is not allowed (if you were outbid in the meantime). How would we build such a system? We can still use the previous design, and just defer the actual billing for a later stage, but let us assume that this is a strong constraint on the system.
Original title and link: Data Modeling for Document Databases: An Auction and Bids System ( ©myNoSQL)
Ayende and Justin pair to model a StackOverflow website clone with RavenDB. And they cover:
- Map/Reduce indexes
- Modelling tags
- Root aggregates
- Active tags
- Built-in caching
- Lazy loading
- Aggressive caching
- RavenDB profiler
Such list would be even more useful with the following classification:
Note: A special mention in this category for OrientDB and Terrastore which even if they might not be largely adopted they are still active projects probably counting a couple of production deployments.
Original title and link: 11 Document-Oriented Databases Which Are 8: CouchDB, Jackrabbit, MongoDB, RavenDB ( ©myNoSQL)