Best architecture for accessing secondary database
        Posted  
        
            by fearofawhackplanet
        on Stack Overflow
        
        See other posts from Stack Overflow
        
            or by fearofawhackplanet
        
        
        
        Published on 2010-05-24T15:19:55Z
        Indexed on 
            2010/05/24
            15:21 UTC
        
        
        Read the original article
        Hit count: 357
        
I'm currently developing an app which will use a Linq to SQL (or possibly EF) data access layer. We already have a database which holds all our Contacts information, but there is currently no API around this. I need to interact with this DB from the new app to retrieve contact details.
I can think of two ways I could do this - 1) Develop a suite of web services against the contacts database 2) Write a Linq to SQL (or EF) DAL and API against the contacts database
I will probably be developing several further apps in the future which will also need access to the Contacts data.
Which would generally be the prefered method? What are the points I need to consider? Am I even asking a sensible question, or am I missing something obvious?
© Stack Overflow or respective owner