On Wed, 2008-12-10 at 09:47 -0500, Mark Ramm wrote: > > > I'm very interested to hear about how TG2 will avoid the scaling and > > traffic issues that hit pownce and twitter. > > Well, there are lots of issues, and without being super-connected to > either Twitter or Pownce, one of the things that seems to have > happened to both early on is that it was difficult for their platform > of choice to connect to multiple databases and handle horizontal > partitioning. > > Beyond that, it was hard for them to manage how many DB hits each page > produced since the ORM's in their platform didn't make it easy to > group sets of db changed together and submit them all at once. Nor > did they have the flexibility that SQLAlchemy provides in grouping > which data will be returned by a request of a particular mapped > object, both because SA provides fine-grained control of what will be > eager-loaded and what should be lazily loaded, and because SA as a > Data Mapper implementation allows objects to map to data from several > tables at once.
You know, a detailed tutorial/article on the above would probably be very good TG2 publicity, as long as you can do so without looking like you're using Twitter/Pownce as scapegoats. Iain --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
