We do almost exactly what you describe for our customers. Here's how using ColdFusion Standard.
One application source. Multiple named instances of that application. So customer A goes to customerA.domain.com It says, hmm customerA you say, this is application customerA ie, application.cfc this.name = 'customerA', application.datasource = 'customerA' etc etc Works like a dream. PS: The single codebase is a dream, you might be tempted at some point to branch, but long term its better to add that feature to your core and have it as a configurable option. Regards Dale Fraser http://learncf.com -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Barry Beattie Sent: Thursday, 7 February 2008 3:15 PM To: [email protected] Subject: [cfaussie] clustering, multiple instances and application design situation: in our business, we do partnership deals with other organisations who we license resources to and then finalise their output on their behalf on our IT systems. we're looking at providing the tools for our partners to logon and use to complete the middle part of the process. There's about 20-30 partners. These "tools" will never be outside our control (ie not on partners servers) and won't be individually customised outside some basic settings (no forking of the code) OK I'll only have two ColdFusion 8 Enterprise server boxes to do this (plus separate DB servers), at least to start with. either - I run all the customers out of one instance of the application and use their OrganisationID to differentiate each partner - sometimes right down to the individual database row level, all in one db. - cluster both boxes and add a hardware load balancer in front of them - additional partners means adding another server into the cluster - I gain on fail-over but lose on application design. or - I run each partner as a seperate CF8 instance off the same codebase, forget about the OrganisationID, and use each instance's CFIDE to point the DSN to the corresponding matching database - one for each partner - don't bother clustering but try and spread the load by grouping customers - additional customers means adding another server to put the new customers on - I have no fail-over but it's a lot cleaner as far as rolling out new customers. any other options? any suggestions? many thanks b --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "cfaussie" 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/cfaussie?hl=en -~----------~----~----~----~------~----~------~--~---
