Strong means all replicas will have the updates after a write returns and all reads after the write will "see" those updates.
Consistent (or eventually consistent) means that all replicas will eventually have the updates after a write and some reads after the write will "see" stale/previous versions of the data. Basically it boils down to trading correctness (possibility of stale reads) for better performance. - alkis On Wed, Mar 17, 2010 at 10:48 PM, prgmratlarge <[email protected]>wrote: > What are strong vs consistent reads? > > On Mar 16, 11:31 pm, "Jason (Google)" <[email protected]> wrote: > > Hi Everyone. Just a quick note that we just uploaded pre-release 1.3.2 > > SDKs for Python and Java to our Google Code project page: > > > > http://code.google.com/p/googleappengine/downloads/list > > > > Both pre-release SDKs include RELEASE_NOTE files that indicate what's > > new, but the App Engine back-ends have not yet been updated, so please > > don't try to use these new features in production just yet. Please > > test your existing applications locally using the new SDK and report > > any bugs as soon as possible. Our next general release will likely > > follow in the next couple of weeks barring any unforeseen issues. > > > > Thanks, > > - Jason > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-appengine%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
