all questions lead to the answer 'Well, hmmm, it depends.'   :)   Something
I would be really surprised about is that of all 20-30 of these partners,
their business requirements would all be exactly the same say 3, 6, or 9
months from now.  Be prepared to fork for a customer, eh?  Perhaps you are
lucky in this.   Maybe you could have separate schemas in the DB for each
partner with a single schema that all the other schemas have access to
housing shared data like tables of states, countries, logs,  etc.  Then for
the web app, upon logging in, the DSN is set pointing to a particular scheme
for the user.  It'd be tough to put 20-30 instances of CF on one box unless
you got like 20+GB of RAM.

DK

On Feb 9, 2008 6:21 PM, Mark Ireland <[EMAIL PROTECTED]> wrote:

> This question was asked om cfAussie:
>
> 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
> _________________________________________________________________
> What are you waiting for? Join Lavalife FREE
>
> http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Flavalife9%2Eninemsn%2Ecom%2Eau%2Fclickthru%2Fclickthru%2Eact%3Fid%3Dninemsn%26context%3Dan99%26locale%3Den%5FAU%26a%3D30288&_t=764581033&_r=email_taglines_Join_free_OCT07&_m=EXT
>
> 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to 
date
Get the Free Trial
http://ad.doubleclick.net/clk;160198600;22374440;w

Archive: 
http://www.houseoffusion.com/groups/CF-Server/message.cfm/messageid:6528
Subscription: http://www.houseoffusion.com/groups/CF-Server/subscribe.cfm
Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.10

Reply via email to