raven db; day to day

Andrea Magnorsky

Document Database JSON Linq Open source Transactional Flexible

No schemas Documents DTO Knowledge re-use In synch with aggregates (DDD) Advanced features

Setup: for production and testing. Indexes

map reduce.

Understanding stale data.

Test strategies Migrations Backup Document design: keep on keeping on.

Embedded

Server

… Sharded

Loads associated documents on first request. Example

At the core of Raven Linq provider Eventually consistent

From http://www.gridgain.com/images/mapreduce_small.png

The result type is not consistent across map and reduce

Not creating the indexes Creating too many indexes (they are costly) The index runs but results are not what you

expected

Basically Map/reduce but with many maps

Remove fields: Loose data Add fields: default values strategy Change: come up with a suitable strategy

Sharding and Replication. Quotas. Expiration. Index Replication (to SQL) Authentication (with Oauth). Authorization. Versioning. Cascade Deletes. More Like This. Unique Constraints.

Shadow copy. Take copies of data directory Raven backup and restore system

Well designed and abstracted Embedded document store

@silverspoon www.roundcrisis.com