DAL vs Web Services
My company is considering changing from using webservices to retrieve data from a sql database to a data access layer utilizing business objects. Has anyone actually use both and can comment on performance differences. Also is a dal the definite way to go, not taking into consideration the time to change over. Finally is there any cases when a dal should not be considered.
We have applications using both windows and web apps. So far we only utilize sql databases. Our web apps run off of web farms.
Let me know if their is more info needed to answer this question correctly.
Thanks
[617 byte] By [
terickso] at [2007-11-20 11:25:35]
# 1 Re: DAL vs Web Services
First, I'd like to make sure that we talk the same language when discussing this issue.
DAL is responsible for direct data access to DB, most of its work is CRUD operations (Create, Read, Update ,Delete)
Making CRUDy web services is considered an antipattern (bad practice)
Check these links:
http://msdn2.microsoft.com/en-us/library/ms954638.aspx
http://weblogs.asp.net/cibrax/archive/2007/01/25/crud-interface-for-a-service-is-a-bad-practice.aspx
Also, controlling transaction boundaries between web service calls won't be an easy thing.
Web services methods should represent a business scenario, or say, a use case. And internal implementation of Web services will still use DAL components to make DB operations.
I believe, your company must have an answer for this question:
Why are we going to expose our system as web services?
hspc at 2007-11-9 13:45:39 >
