Hi, I would like to hear views from you guys on having multiple versions of a web application.
We are developing a web solution for our clients to handle their business processes. With reality in check, clients' requirements change over time; sometimes adding a new field, changing the calculation logic etc. When it was still a small scale solution, whenever an upgrade occurs, we will upgrade any existing data to the latest change i.e by having a empty property for it. I would admit this isn't the best of scenarios as old products that previously don't possess certain properties are now 'new' again which doesn't reflect the product correctly.
I am looking for a solution to introduce versioning to this solution before things get out of hand. What I've come up with is like this:
Realising that data is semi-structured (it changes from time to time), we've decided to go with an XML / XSLT approach. Storage of the data wil ...
Go to the complete details ...