Ian Bambury wrote: > 1000 clubs with 10 squash/tennis courts each with 1-hour bookings, that's a > quarter of a million records per day or getting on for 100 million records > for the year.
The courts are open 24 hours a day? > Is that really the best way to go? Does it really scale? Well, one way or another you're going to have to scale to some fraction of that. If the courts are booked 50% of the time then you'll still need to record 50 million bookings a year. You could save space by using a bitmap. Have one entity for each hour which contains a blob with one bit for each court. The problem with this is that only answers the specific query you mentioned. If you want to know something like who booked a court you'll still need the 50 million booking records. It would also scale terribly, as there's likely to be a lot contention for each hour's entity as it gets closer to that day. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
