I have an application I've created in PHP that runs on a single LAMP via managed hosting, and I'm looking to take a fresh and ground-up look at how I would re-implement my applications for scalability and performance.
Currently I have separate databases that I query across, here's a pseudo description of what it looks like: - Main application (users / groups / forums / posts - 40 tables, 300k rows, 20mb dump) - Logging (milestones / events, 6 tables, 400k rows, 20mb dump) - Online Products Store (products / deliveries / receipts - 10k rows, 4mb dump) - Games and Scores and Saved Data (10 tables, 20k rows, 5mb dump) I'd like to use CakePHP and have the user only exist once, but have them able to access the services across all of the applications as I add additional services for the users. Can you point me to any tips or tricks on the design, or links to where I can read up and make decisions on how I would construct this application with the intent of sharing data between databases and or between cakes? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" 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/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
