I have a website that I'm trying to add an application too. This new application is built around its own membership structure. I want to maintain my current membership structure and the app work with it.
I am seeing two options. First option is to compare and contrast both structures and add to my existing one or slightly modify it to be more similar to the structure of the new app. Once I take that as far as I can, I then start going through the source of the new app and changing how it interacts with the membership structure to accomodate the new data source..
Second, keep both memberships and have redundant data. The new app would still feed on the session from my current setup, but any time the app needed member data it would look to its own source. As people updated records, both tables would have to be modified simultaneously, and I would have to hope that the sources remained consistent. I would probably have to create some checks that would verify/check for inconsistencies, and pick one db to be the authoritative source.
thoughts?
I am seeing two options. First option is to compare and contrast both structures and add to my existing one or slightly modify it to be more similar to the structure of the new app. Once I take that as far as I can, I then start going through the source of the new app and changing how it interacts with the membership structure to accomodate the new data source..
Second, keep both memberships and have redundant data. The new app would still feed on the session from my current setup, but any time the app needed member data it would look to its own source. As people updated records, both tables would have to be modified simultaneously, and I would have to hope that the sources remained consistent. I would probably have to create some checks that would verify/check for inconsistencies, and pick one db to be the authoritative source.
thoughts?