> 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. Of course both Pownce and Twitter eventually got to the point where they were using hand-coded SQL and multiple databases for lots of things, and were still having database scalability issues. And there's no magic that the framework can do to fix that. But SQLAlchemy continues to shine as a toolkit even when you're not using the ORM. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
