Innovative Multi-Server Configuration Uses
Ben Forta posted this item on CF-Talk while discussing the nuances of moving to a multi-server instance. I thought it was a great illustration of some of the uses of CF Multi-server.
Ben Forta wrote:
It sounds like you are considering dedicated specialized instances, and I am a big fan of this. There is one customer I work with who has several sites in a single instance, like you do, but they have also created specific instances for specific needs. They have one that just does mailing, it receives requests from other instances, and process them. They have another which executes report requests on scheduled intervals. And another that builds Verity indexes when needed. These specialized instances require fewer threads, fewer data sources, no RDS and debugging (which you'd never want enabled on production servers anyway), and so on. That works very well. Of course, you may also want separate instances for specific apps, but that is a separate discussion.
I especially love the idea of a specialized instance for verity indexes. Re-indexing Verity collections is a huge resource hog, and larger collections can cause problems. I don't know why I never considered this approach before - very ingenious.
2 Comments
-
We use a separate instance to do all our batch processing, which has helped with the load on the public-facing instance. We're also in the midst of a customer-by-customer migration from one version of one of our apps to a new version, so we just have the new version (which is radically different architecturally) running in a new instance. Once everyone is migrated over to the new version we'll just shut down the old instance. -
Hmmm.. great idea. Kinda like "normalized" server instances, where you are trying to eliminate redundancy and specialize each instance. A good actualized approach.
Sami
Sites to Watch
Aggregators
RSS
