Having a single counter for records in a distributed system will create a bottleneck when the application needs to scale to handle an increased load (such as an increased number of simultaneous users). One solution is to use a collection of counters (called a sharded counter in the video below) to solve the load scaling problem. This is described from about 0:40:40 in this video:
http://www.youtube.com/watch?v=FZ-aagsMv40 The Google App Engine team could perhaps have included a general counter in the API, but one risk is that application developers then would overuse counters without having design for distributed systems in mind. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
