2008/11/6 Ross Ridge <[EMAIL PROTECTED]> > > 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?
Well, no, not all of them, anyway, I suppose, but some clubs will open at 6, and some will have squash courts until late or floodlit tennis and the system could be used for other things, and the actual booking times and lengths may vary from club to club and the there are time differences, and if *any* of them are open 24/7 then the search needs to be able to accommodate it and we could have 100,000 businesses around the world if it takes off :-) OK, maybe not, but we don't know what the figure will be and they could easily exceed 1000 - 10,000 is a billion records, and you would still need a billion records even if there is only one booking. I'm talking high-pathetically here, you understand :-) But really the question is a more general one of how do you approach this scenario with an open-ended number of clubs? In a normal relational database, you could hold just the booked slots and with one SQL request, get the top 20 available courts by time, distance or whatever. My client is very keen on using GAE, so I need to find a scalable way of doing it, or a very solid reason to use a relational DB. Ian --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
