﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>Ayende Rahien commented on Enhancing the RavenDB consistency model</title><description>Martin,
We had some issue with the server datetime, which caused it to drift.
Basically, it handles changes just fine.
If you add a property, it will be added to the document on the first save on the new value.
If you remove a property, it will be remvoed on the next save.
The only thing that requires work is renaming a property, and we have explicit support for doing that.

As for memory usage, that really depend on the actual usage. The short answer is that it shouldn't take too much memory, and is usually much more effiecnt (joins takes a LOT of memory.</description><link>http://ayende.com/22529/enhancing-the-ravendb-consistency-model#comment19</link><guid>http://ayende.com/22529/enhancing-the-ravendb-consistency-model#comment19</guid><pubDate>Wed, 29 Jun 2011 19:25:01 GMT</pubDate></item><item><title>Ayende Rahien commented on Enhancing the RavenDB consistency model</title><description>Avish,
A client in this sense is each document store. The scenario at hand is that each client is running in a different application / process.</description><link>http://ayende.com/22529/enhancing-the-ravendb-consistency-model#comment18</link><guid>http://ayende.com/22529/enhancing-the-ravendb-consistency-model#comment18</guid><pubDate>Wed, 29 Jun 2011 19:22:44 GMT</pubDate></item><item><title>Avish commented on Enhancing the RavenDB consistency model</title><description>I still can't understand how you distinguish one client from another. Do they identify during the initial connection? 
In other words, how (if at all) can I make the user wait for the item they just created, without waiting for all other users, while being served by multiple web servers without a sticky session?</description><link>http://ayende.com/22529/enhancing-the-ravendb-consistency-model#comment17</link><guid>http://ayende.com/22529/enhancing-the-ravendb-consistency-model#comment17</guid><pubDate>Wed, 29 Jun 2011 19:06:31 GMT</pubDate></item><item><title>Martin commented on Enhancing the RavenDB consistency model</title><description>Something must be wrong with your blog and the way it handles dates, as your answer comes before my question (I asssume you dont have magic powers) :)

The date for my question is 06/29/2011 02:03 and the date for your answer is 06/28/201110:42 PM.


Can you point me to an article talking about RavenDB and how to handle changes in the the document.

That is my biggest concern with any NoSql solution, because i am not experienced and i acknowlegde that, so i know that what i start out with will probably not be what i want to end up with. It seems impossible to figure out all the data i will need in a document from the start.

Most likely as the project grows I will need to change the structure of the document and maybe rename something and merge data from one document to another and stuff like that, but how do i handle that easily with RavenDB?

Does RavenDB consume a lot of memory compared to etc. Ms Sql Server because of all the indexes and that the data is not as normalized as in a RDBMS ?</description><link>http://ayende.com/22529/enhancing-the-ravendb-consistency-model#comment16</link><guid>http://ayende.com/22529/enhancing-the-ravendb-consistency-model#comment16</guid><pubDate>Wed, 29 Jun 2011 15:24:07 GMT</pubDate></item><item><title>Martin commented on Enhancing the RavenDB consistency model</title><description>Have you remembered to document this feature ?

...and also the session.Advanced.DocumentStore.AggressivelyCacheFor() feature (and all other features you mention here on the blog).

The documentation on the on the RavenDB website seems very limited compared to how many features I have read about here on your blog.</description><link>http://ayende.com/22529/enhancing-the-ravendb-consistency-model#comment14</link><guid>http://ayende.com/22529/enhancing-the-ravendb-consistency-model#comment14</guid><pubDate>Tue, 28 Jun 2011 23:03:58 GMT</pubDate></item><item><title>Ayende Rahien commented on Enhancing the RavenDB consistency model</title><description>Martin,
Yes, we are working on the docs, we intend to release a new website soon, and that is probably when we will have all of the new info there.
You can see the pending docs tasks here: https://github.com/ravendb/ravendb/issues</description><link>http://ayende.com/22529/enhancing-the-ravendb-consistency-model#comment15</link><guid>http://ayende.com/22529/enhancing-the-ravendb-consistency-model#comment15</guid><pubDate>Tue, 28 Jun 2011 19:42:32 GMT</pubDate></item><item><title>Jonty commented on Enhancing the RavenDB consistency model</title><description>Awesome. This solves the problem we have with Patching denormalized data, where we need to make sure our index includes everything that has been written.</description><link>http://ayende.com/22529/enhancing-the-ravendb-consistency-model#comment13</link><guid>http://ayende.com/22529/enhancing-the-ravendb-consistency-model#comment13</guid><pubDate>Thu, 23 Jun 2011 08:52:25 GMT</pubDate></item><item><title>Ayende Rahien commented on Enhancing the RavenDB consistency model</title><description>Justin,
NuGet will be updated on Monday</description><link>http://ayende.com/22529/enhancing-the-ravendb-consistency-model#comment12</link><guid>http://ayende.com/22529/enhancing-the-ravendb-consistency-model#comment12</guid><pubDate>Thu, 23 Jun 2011 03:50:53 GMT</pubDate></item><item><title>Justin A commented on Enhancing the RavenDB consistency model</title><description>*hug* 

awesome awesome awesome.

I'm going to start to set this as a default and see how things pan out. so kewl!

Has NuGet been updated, yet?</description><link>http://ayende.com/22529/enhancing-the-ravendb-consistency-model#comment11</link><guid>http://ayende.com/22529/enhancing-the-ravendb-consistency-model#comment11</guid><pubDate>Thu, 23 Jun 2011 01:16:16 GMT</pubDate></item><item><title>Michael L Perry commented on Enhancing the RavenDB consistency model</title><description>This is a feature that I've often referred to as "local consistency" to distinguish it from eventual consistency. Most CQRS implementations don't have this feature. It does quite a lot to put a users mind at ease, I i insist upon it. Glad to see you've added it to Raven. </description><link>http://ayende.com/22529/enhancing-the-ravendb-consistency-model#comment10</link><guid>http://ayende.com/22529/enhancing-the-ravendb-consistency-model#comment10</guid><pubDate>Wed, 22 Jun 2011 17:02:01 GMT</pubDate></item><item><title>Ayende Rahien commented on Enhancing the RavenDB consistency model</title><description>Randall,
I thought about making this the default, but I am not sure yet, we'll see after we have some time with this feature in the field.</description><link>http://ayende.com/22529/enhancing-the-ravendb-consistency-model#comment9</link><guid>http://ayende.com/22529/enhancing-the-ravendb-consistency-model#comment9</guid><pubDate>Wed, 22 Jun 2011 16:14:52 GMT</pubDate></item><item><title>Randall Sutton commented on Enhancing the RavenDB consistency model</title><description>You are a genius! You have just solved the only pain point I have experienced with RavenDB. I concur with having this on by default, but that is just me :)

Thanks!
</description><link>http://ayende.com/22529/enhancing-the-ravendb-consistency-model#comment8</link><guid>http://ayende.com/22529/enhancing-the-ravendb-consistency-model#comment8</guid><pubDate>Wed, 22 Jun 2011 15:24:49 GMT</pubDate></item><item><title>Ayende Rahien commented on Enhancing the RavenDB consistency model</title><description>Khalid,
This is probably better, yes.
</description><link>http://ayende.com/22529/enhancing-the-ravendb-consistency-model#comment7</link><guid>http://ayende.com/22529/enhancing-the-ravendb-consistency-model#comment7</guid><pubDate>Wed, 22 Jun 2011 14:10:32 GMT</pubDate></item><item><title>Khalid Abuhakmeh commented on Enhancing the RavenDB consistency model</title><description>I ran into this issue, but my solution at the time was adopting the Rails methodology of saving a new item. First you save the document, then redirect to a show/details page. Since you can query off the id directly you don't have to wait for an index to update. The user is just looking for confirmation that their work has been saved, so a details page is just as much confirmation as a list. Also the user will most likely want to enter another item, so you can transition them back to an insert/edit page while the indexes update (super fast).

Does this solution mean that RavenDB users should stop using the WaitForNonStaleResultsAsOfNow() method and use this (as long as they upgrade)?

</description><link>http://ayende.com/22529/enhancing-the-ravendb-consistency-model#comment6</link><guid>http://ayende.com/22529/enhancing-the-ravendb-consistency-model#comment6</guid><pubDate>Wed, 22 Jun 2011 13:59:12 GMT</pubDate></item><item><title>Ayende Rahien commented on Enhancing the RavenDB consistency model</title><description>Eric,
"Client" as in DocumentStore == machine.
Everrett's case was literally different apps contacting the same server, so each would only need to consider its own changes.</description><link>http://ayende.com/22529/enhancing-the-ravendb-consistency-model#comment5</link><guid>http://ayende.com/22529/enhancing-the-ravendb-consistency-model#comment5</guid><pubDate>Wed, 22 Jun 2011 13:45:24 GMT</pubDate></item><item><title>Eric J. Smith commented on Enhancing the RavenDB consistency model</title><description>Sounds like a pretty awesome feature.  Maybe even something that should be on by default?  Guess I should look to see how it works because I don't understand how it would know what writes are mine in a stateless world like the web.</description><link>http://ayende.com/22529/enhancing-the-ravendb-consistency-model#comment4</link><guid>http://ayende.com/22529/enhancing-the-ravendb-consistency-model#comment4</guid><pubDate>Wed, 22 Jun 2011 13:32:08 GMT</pubDate></item><item><title>Ayende Rahien commented on Enhancing the RavenDB consistency model</title><description>Eric,
The information is held at document store, not the session level.
</description><link>http://ayende.com/22529/enhancing-the-ravendb-consistency-model#comment3</link><guid>http://ayende.com/22529/enhancing-the-ravendb-consistency-model#comment3</guid><pubDate>Wed, 22 Jun 2011 13:27:14 GMT</pubDate></item><item><title>Eric J. Smith commented on Enhancing the RavenDB consistency model</title><description>How does this work in web scenarios where the next request would be from a new session instance?</description><link>http://ayende.com/22529/enhancing-the-ravendb-consistency-model#comment2</link><guid>http://ayende.com/22529/enhancing-the-ravendb-consistency-model#comment2</guid><pubDate>Wed, 22 Jun 2011 13:23:19 GMT</pubDate></item><item><title>Everett Muniz commented on Enhancing the RavenDB consistency model</title><description>As the user referred to here: "the user couldn’t just use WaitForNonStaleResultsAsOfNow(), or to be rather more accurate, he was already using it, but it wasn’t working" I obviously think this is a buh-rilliant feature.  The implementation seems really clean and should be really easy to implement.  Now, I'm sure you feel this coming...wait for it...wait for it...so when's the next stable release :-).</description><link>http://ayende.com/22529/enhancing-the-ravendb-consistency-model#comment1</link><guid>http://ayende.com/22529/enhancing-the-ravendb-consistency-model#comment1</guid><pubDate>Wed, 22 Jun 2011 12:35:37 GMT</pubDate></item></channel></rss>