On 9 May 2012 21:51, Steve <[email protected]> wrote: > I have such an application, albeit a small one with multiple databases - one > per customer. I store all the users in a single, separate database, and for > each user, store a reference to their particular database. Once > authenticated, I use InstancePerContext to build the appropriate database > model. It works fine.
Something I've frequently seen is putting memcached in front of the user/session database, this allows you to abstract away (and denormalize if necessary) that database nicely and only worry about your application/site database in most of the application itself - especially for mass hosting sites, or dealing with large clusters of split databases (by region, country, white-label, etc) Cheers, A -- Aaron J Trevena, BSc Hons http://www.aarontrevena.co.uk LAMP System Integration, Development and Consulting _______________________________________________ List: [email protected] Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
