Architecture/Design for maintaining rapid release RRS feed

  • General discussion

  • We have a Silverlight web application consisting of layered architecture ( specifically the UI layer, Service layer using WCF and DAL layer). Currently in case of new release, the updates gets pushed to the customer automatically. Now, we want to maintain atleast 3 live versions of the software. Client will decide whether they want to upgrade to the latest version or not or they want to stick to the older version, update should only happen only for the previous case. We have done some sort of analysis on this. We were thinking of maintaining separate codebase for UI and WCF for all three versions. Database code (SP, Views) will be separated based on separate db schema created for different versions. e.g. if there's a SP named GetEmployee and there are software versions 1.1,1.2,1.3, then we will be creating three different schema for 1.1,1.2 and 1.3 and three different copies of GetEmployee under these three schema. One of the drawback of this approach I can think is maintainability. Is there any industry standard approach available which is better than this. Please suggest.



    Thursday, May 29, 2014 12:24 PM