Web Services as Data Access Logic Component

From: as_lev (as_lev_at_discussions.microsoft.com)
Date: 03/13/05


Date: Sun, 13 Mar 2005 05:57:01 -0800

Hello!

First, I want to reccomend the Fantasticthe article about distributed
applications:
http://msdn.microsoft.com/architecture/default.aspx?pull=/library/en-us/dnbda/html/BOAGag.asp

I am designing a distributed application with a presentation layer as a
windows forms (we think to switch to the web on the future), a Business Logic
as web services (which act more like a Data Access Logic Component) and a
Data access layer as the Microsoft data access application block. The
Business processes will take place both at the web services functions and the
Stored procedures.

And here are my questions:
1. Does this architecture is accurate?
2. Do I need to define the business entities within the web services only to
import them to the UI or to define them also in my presentation layer? Maybe
I need to do both using Interfaces?

Thanks in advance!!



Relevant Pages

  • Data Access and SOA
    ... an insurance business: Insured WS, Claim WS, Client WS, etc.) and were using ... Incorporate the data access in the individual web services (i.e. for ... WS layer...why not just allow the client to do the data access? ...
    (microsoft.public.dotnet.distributed_apps)
  • Re: Which Layer to use
    ... Business Logic Layer ... Are you suggesting that the user has a thick client where presentation and business live and that client talks to the DB via the Data Access layer through web services? ...
    (comp.object)
  • Re: interfacing with data layer
    ... I think that the correct solution is to build a business layer between ... SQL Server Stored Procs as the data access tier. ... The UI layer is also dependent on ADO.NET ... > may end up with web services at both spots, ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Just tell me why ? so confuse...
    ... architecture in that case would have a presentation layer communicating ... performance hit caused by web services because we are gaining so much ... more towards our overall enterprise architecture. ... exposed a subset of those facades to other applications that needed to ...
    (microsoft.public.dotnet.framework.aspnet.webservices)
  • Securing TableAdapters/xds files
    ... was using webservices which used dataadapters to retrieve and update ... the web services were called from the presentation layer and were ... on a seperate server from the presentation layer. ... I've been interested in using the objectdatasource since there's so ...
    (microsoft.public.dotnet.framework.aspnet.security)