Hello folks at Google, I was wondering if you would be open to describing certain internals of the Task Queue so that we can get a better understanding of it, and potentially use the learnings to replicate it for use as a Task/ Message Queue. We have a requirement for a task queue, so I was wondering if there is a chance to understand what appengine is using. I have a few specific questions too. I'll just go ahead and write them out, so if it is okay, then you could reply to those.
1. Are the tasks persisted on stable storage when they are added to the queue? 2. Is there special handling for named tasks and tasks with an ETA? 3. Can you disclose numbers as to how well a task queue instance on a single machine performs (with reliable message delivery and no ETA/ named tasks)? 4. What is the typical load on a single task queue server instance? 5. What is used to communicate between different task queue instances and between the appengine API and the task queue (protobuf, etc..??) 6. Are you planning to open source the task queue server any time soon/ Do you use a message queue that is available off the shelf and build stuff around it? Regards, -Dhruv. -- 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.
