aspnetdev
asked on
3 Tier Winform Application
Hi,
I have a winform application that is using a webservice to communicate to the database.I made a architecture diagram as follows
UserInterface Tier Middle Tier Database tier
UI ---------------------> Webservice -->Dataaccess ---------->Database
Components
Does this approach make any sense?Can any one comment on this?
Thanks
I have a winform application that is using a webservice to communicate to the database.I made a architecture diagram as follows
UserInterface Tier Middle Tier Database tier
UI ---------------------> Webservice -->Dataaccess ---------->Database
Components
Does this approach make any sense?Can any one comment on this?
Thanks
if you need to access your business objects across the internet then this is exactly how to do it. If this is purely in a LAN environment the the webservice will introduce some overhead to the messaging with your business objects. If performance is very important you may want to move to remoting (using tcp/binary channel/formatter) or possibly COM+ (Enterprise services) and interop.
I agree with Zippit, webservices can be overkill in most situation where you don't have to go over the web.
You may use a very similar architecture (and yet be opened to the web) by using WCF. See http://netfx3.com/content/WCFHome.aspx
You may use a very similar architecture (and yet be opened to the web) by using WCF. See http://netfx3.com/content/WCFHome.aspx
ASKER
thanks, for the comments but i would like to know will my webservice come under the business layer and UI in the GUI layer?
If you are speaking only of (logical) layers, we normally limit the number of 3. Data-Business-Presentation . A Web service is clearly in the Business layer because it does not handle controls (at least should not).
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.