Click here to Skip to main content
15,868,141 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
I am thinking of making our DataBaseAccess common/reusable to all our internal/external applications. I have many small console, windows, windows service, web service & web applications as clients accessing the database. Many applications deployed in multiple servers.
While in the process the thought that came into my mind is as below:

Option 1
===========
Create a DataBaseAcces using Entity Framework and expose the required methods through a WCF Web Service. This way if any table structure changes in the future, I need to update the model only in one place, instead of updating mutliple places/projects.

There can be a performance degradation here.

Option 2
===========
Create a class library for DataBaseAccess(with Entity Framework) and deploy to the GAC of each servers. But this again needs redeploying to multiple servers if any DB changes occur.

Also Is it good have all applications access same DataAccess layer, the reason being if for some reason the server where the dataaccess layer is deployed goes down, then it will affect all the applications.


These are the options I think as of now.

I would appreciate your suggestions/ideas/recommendations.
Posted
Updated 25-Apr-14 6:41am
v2
Comments
Sunasara Imdadhusen 26-Apr-14 5:28am    
What you tried!!!

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900