Home All Groups Group Topic Archive Search About

Distributed 3 Tier & WebService Design Question

Author
17 Dec 2005 11:42 AM
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

--
Sent via .NET Newsgroups
http://www.dotnetnewsgroups.com

Author
20 Dec 2005 3:57 AM
spalding
Hi there,

Well the way I look at webservices is as  just another way of presenting data (in this case in a raw, XML-based manner).

Therefore, your webservices should be able to share your business objects with your Web UI layer.

There may be occasional pieces that perhaps utilize lower level functionality of your business object tree, but I don't think your webservices should be coded against your data access objects and certainly not directly to the underlying DB.

It is important to remember that when you provide an enduser interface, whether web app, web service or desktop app, you will want to enforce your system's business rules from a centralized location (hence business objects). The last thing you want to do is make a business rule change in one part of your app, then have to make the exact same change to another part (or worse still, forget to make the change).

Hope this helps. -- spalding ------------------------------------------------------------------------ Posted via http://www.codecomments.com ------------------------------------------------------------------------

AddThis Social Bookmark Button