« Handing and Testing DeadlineExceededError | Main | Debugging Facebook AppEngine application locally »


Kyle Roberts

You can create a set of 100 task queue elements and taskqueue.add() them 100 at a time (per rpc call). I would suggest the mapreduce API as a better alternative to executing your migration method from the remote api or interactive console. This will eliminate the need for task queue or deferred API.


how do you deal with updating of reference properties. We are stuck with them.


I don't buy the Cache argument I'm airfad. It implies all updates are occuring only through HTTP? how practical is that in reality?If I have an application running inside AMAZON's network that applies some general discounting rules then all cached URI's that represent books are immediately out of date anyway?It is not as if because we expose our data restfully, all of a sudden that is going to be the only way you can update it. So I don't see why you should enforce some rules about PUT granularity in your REST implementation, it makes no sense to me.I also don't buy the HTTP swamping argument either. Updates are generally a lot less frequent than gets, so why not go granular on the update. If you have a number of tuples to update sure go more chunky, that is a standard piece of distributed architecture advice, but if you have only one thing to update, why pass everything else? That can have some nasty side effects too, you might now introduce the last update problem, because of optimistic concurrency issues, i.e. the server doesn't actually know what fields you are trying to update so it assumes you are trying to update everything. If in our distributed systems we mandate chunkyness we simply further increase the systems brittleness.

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Your comment could not be posted. Error type:
Your comment has been posted. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.


Post a comment

Your Information

(Name and email address are required. Email address will not be displayed with the comment.)