Data Repository Class Vs WebService

[Dave Johnson]

My ASP.net 1.1 online cinema reservation system is Developed in 3 Tiers:
1-DataAccessTier "Data Repository Class"
2-Business Tier "Set of Business Classes"
3-Presentation Tier "set of WebUserControls & aspx pages"

if i want to make a WebService that enables its users to interact with
the system, In the search for the ultimate Architecture, Should the
Design be:

1- Connect the WebService to my DAL and my Data Repository class
interact with the database through the Webservice?
OR
2- Remove the Data Repository Class and use the WebService as my way to
connect to the database?

OR

there is any other Better Solutions from your Previous Experiences ?????

Please if you have the Experience to make a good guidance in this
particular problem try to suggest different approaches by stating the
Advantages of this approach on the other as a proof that this is BETTER
than the other. I am sure it’s a common problem as i am new to
webservices and there is a Better approaches than what I thought about.

“What is the BEST way to Do IT?”

Thanks


Sharing makes All the Difference

 

[Sahil Malik [MVP C#]]

First Q - why do you need all 3 tiers?

Assuming you've asked yourself that question,

1- Connect the WebService to my DAL and my Data Repository class
interact with the database through the Webservice?
OR
2- Remove the Data Repository Class and use the WebService as my way to
connect to the database?

Neither.

The purpose for WebServices is to create loose coupling between isolated
peices of functionality in your application - this gives you flexibility as
your application grows. The trade off of loose coupling is lower control,
more unexpected crap, and frankly suckier performance.

The place for webservices is not at your DAL - where performance is tight
coupling is critical.

- Sahil Malik [MVP]
ADO.NET 2.0 book -
http://codebetter.com/blogs/sahil.malik/archive/2005/05/13/63199.aspx
__________________________________________________________

 

[Dave Johnson]

i thought about building a webservice that share the same Interface of
the Data Repository Class(DAL)

so everyone can further build system that connects to Cinema Database
and get seat avaiability and performances time,date, etc


does that makes sense?

Sharing makes All the Difference