Merge Schema or Exchange Information at Service Layer RRS feed

  • Question

  • Hi all,

    We have 2 similar applications that are similar in architecture but have differences at database schema level. Both applications want to use the same user information but store it differently. Application 1 will be the master, Application 2 will be slave. 

    Both architectures have a service layer sitting on top of unit of work, repository pattern, ef etc. 

    There are 2 options that I see: 

    1. Merge schemas 

    2. Exchange/Replicate User Information using the Service Layer - merge applications in a single MVC web application. To the user - it is a seamless experience. 

    Option 1 is a merged approach that I see would have a long dev cycle. 

    Option 2 is "modulising" the product as such - with multiple databases. Longer term the admin module containing all core info (user info for example) - could be the core module used by other modules? 

    Any thoughts welcome!


    Thursday, September 11, 2014 10:46 AM