This project is read-only.

Dual Data Center Deployment

Topics: General
Oct 5, 2011 at 3:35 PM

We are looking to deploy Orchard in two of our datacenters. Initially we were planning Live/DR with a mirrored SQL server in the 2nd datacenter.

The requirements now are to have both datacenters live/live with Orchard Frontends. In addition, we need to enable live authoring in both datacenters.

Does anyone have any thoughts on extending Orchard, so it will write to 1 datacenter as primary and read locally. In the past we have done things where when a item is inserted/updated, we would write/read from the same datacenter for a few minutes. (We would keep track of this in a session cookie, so irrespective of datacenter which the user hits using the browser, the content will be read from the master and cached ofcourse, the cache will be application specific knowing what cache entries to invalidate when content item is inserted/updates). Considering the # of writes is not that much, this could in theory work for us.

If there are any other ideas on how to solve this, please do share.



Oct 5, 2011 at 8:44 PM

The new task lease feature in 1.3 might help, maybe.