Distributed 3 Tier & WebService Design Question -- dotnet distributed apps

dotnet distributed apps : Distributed 3 Tier & WebService Design Question

Dave Johnson
12/17/2005 3:39:15 AM

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

carion1
12/17/2005 9:25:14 PM

The short answer is, there isn't one. Every project is different with
different requirements. With out more information it is difficult to give
you an appropriate answer for your particular project.

Do the business and data layers need to be exposed to say a 3rd party vendor
or branch location across the internet? Will you have multiple types of
UI's possibly on different types of systems? For instance, maybe Mono/linux
is planned in the future or a win32 UI. How many users will you have and
what is the expected level of performance? You get the idea.

--

Derek Davis
ddavis76@gmail.com

[quoted text, click to view]

Klaus H. Probst
12/17/2005 10:25:25 PM

There is no one-size-fits-all answer to these types of questions, but in
general you want web services to function as "adapters" for your business
logic. Web services are an interop and transport mechanism, not a platform.
They should only expand your BLLs contact surface.

--
Klaus H. Probst, MVP
http://www.simulplex.net/

[quoted text, click to view]

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about dotnet distributed apps

View Other Months
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008

home · blog · groups

Questions? Comments? Contact the dn