Just to let you know, the book is pretty much edited, that means that you won’t have to suffer through my horrible sentence structure.

You can read this here.

What remains to be done now is for me to go over the book again, verify that there aren’t any issues, and we are done.

In other words, we are now “Done, Done” in the “Done, Done, Done” scale.

The Inside RavenDB 4.0 book is done. That means that all of the content is there and it covers every aspect of RavenDB.

There is still quite a bit to be done (editing and re-reads, mostly), but the the hardest part (for me) is done. I got it all out of my head and into a format where others can look at this.

You can read the draft release here.

The book cover:

1. Welcome to RavenDB
2. Setting up RavenDB
3. Document modeling
4. Client API usage
5. Batch processing with subscriptions
6. Distributed RavenDB Clusters
7. Scaling RavenDB
8. Sharing data and ETL processes
9. Querying
10. Indexing in RavenDB
11. Map Reduce and aggregations
12. Managing and understanding indexes
13. Securing your RavenDB cluster
14. Encrypting your data
15. Production deployments
16. Monitoring and troubleshooting
17. Backup and restore
18. Operational recipes

A total of 18 chapters and 570 pages so far.

I’m still missing an index, intro and a bunch of stuff, but these are now more technical in nature. No need for creative juices to pump to get them working.

Feedback is welcome, I would really appreciate it. You can read it here.

You might have noticed that I’ve slowed down writing blog posts. This is because pretty much every word I write these days goes into the book.

I just completed chapter 17, and we are now standing at around 550 pages in length, and there is only one chapter left.

Chapter 17 talks about backup and restores, how they work in RavenDB and how to properly manage your backup strategies in RavenDB. It sounds deathly dull, but it can actually be quite interesting, since backing up of a distributed database (and restoring one, which is harder) and non trivial problems. I hope that I did justice to the topic.

Next, maybe even as soon as early next week is Chapter 18, operational recipes, which will cover all sort of single use case response from the operations team to how to deal with various scenarios inside RavenDB.

You can read the draft here and your feedback is always appreciated.

I’m happy to announce that Chapter 16 is the Inside RavenDB 4.0 book is done.

Chapter 15 talked about production deployment and Chapter 16 talks about monitoring and troubleshooting.

As always, I would really appreciate any feedback you have.

This might be interesting to anyone who want to do a deep dive into how RavenDB security and encryption works, Chapter 14 talks about the details of how RavenDB encrypts data, manages key and in general keep your data safe.

You can get the draft book here.

I just released another update to Inside RavenDB book, with chapter discussing advanced indexing scenarios and how RavenDB handles security, encryption in transit and authentication.

The Inside RavenDB book is rapidly closing on the 400 pages mark (it is currently 371 pages!). I just finished writing Chapter 11, talking about map-reduce indexes.

Go ahead and read it, feedback is (very) welcome.

The Inside RavenDB 4.0 book just got an update, you can download the new release in the link. It currently has 10 chapters and cover a lot of materials. New in this release is in depth coverage of indexing.

Note that some of the earlier details might have changed a bit (usually configuration name changes), I’m going to go over and fix them as part of the release process.

There are also the upcoming RavenDB Workshops in San Francisco and New York next month, if you want to learn about RavenDB directly from me .

We’ll also have a booth at the Developer Week conference in early February in San Francisco.

I’ve just completed writing chapter 6 (distributed RavenDB) and pushed a preview up. This put the page count at over 200 pages so far, with another two thirds or so left.

This chapter was really hard to write, and I would really appreciate any feedback that you have on the text and on the distributed nature of RavenDB 4.0 in general. It is very similar and a different beast entirely then 3.x.

I have just completed writing the 3rd chapter for Inside RavenDB 4.0, and the full book is available here (all three chapters of it). It is just under 100 pages in size, and I’m afraid that at this rate this is going to be a massive tome.

The content so far covers setting up RavenDB 4.0 and doing basic CRUD operations, then goes on to deal with modeling documents inside RavenDB.

Any and all feedback is welcome.