Architecture/Design for maintaining multiple version of an application database

  • We have a Silverlight based application which currently supports only one production version. Idea is to support three concurrent versions of the same application and user will switch to the newer versions based on their interest or they can still continue with the older version.

    We still have to use the existing database for all these three versions.

    What is the best way to architect this so that we can differentiate the code between the versions and still keep the data in sync and run all the versions in parallel.

  • Hello Saikat,

    Pl. do not post the duplicate thread on the multiple places. It will creat confusion and difficult to track the thread.

    Cheers.

    ---------------------------------------------------
    "Thare are only 10 types of people in the world:
    Those who understand binary, and those who don't."

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply