Last post Nov 15, 2017 02:53 AM by Edward Z
Nov 14, 2017 04:31 PM|pulikkan1|LINK
We have different applications in our portfolio. All applications have their own databases and all applications has some redundant tables and data inside those tables like Customer table is there in all 3 applications with same data.
How best we can keep the common data in one place(remove the redundancy). How best if we create separate WEB API for each applications or one WEB API for 3 applications will be better?
Nov 14, 2017 06:44 PM|DA924|LINK
How best we can keep the common data in one place(remove the redundancy).
I suggest that you find more articles and examples covering the information in the link.
How best if we create separate WEB API for each applications or one WEB API for 3 applications will be better?
That's your choice as to how you do it, but what you should understand is how to use the Repository and possibly the DAO pattern with DAO implemented in a Data Access Layer.
Nov 15, 2017 02:53 AM|Edward Z|LINK
How many methods did you provide for application?
If not much, I would suggest you design your structure like three applications -> one web api provide different methods-> one database provide tables.
For this way, one database will reduce the repeat tables and convenience to use. One web api combine application and database, and provide different methods for different purpose. It will be convenience to control the web api.