I would agree that splitting the code into plugins would make the most sense as far as extensibility goes--each developer you outsource to gets the code for the plugin(s) they are working on, and they shouldn't need anything else.
For scalability regarding the number of users you can support and server performance, Varnish can help a lot in cases such as this (Steam, Twitter, Facebook, LinedIn and others all use Varnish). You can run Varnish on all your web servers, and they'll cache and serve the actual content from your main web server as if it were static content from wherever you're running Varnish... with all the speed and performance benefits of serving static content. You don't *have* to touch your CakePHP code to get Varnish working, it's completely non-intrusive--although by default it won't cache any page having a cookie or session in it. However, you *can* modify your CakePHP code to take advantage of some of Varnish's more powerful caching features to reportedly increase your website performance by "orders of magnitude." Anyway, I just wanted to expand on the previous poster who mentioned Varnish--in my experience it has been a powerful tool for websites which have a lot of traffic. Thanks, Ben -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php
