n-tier design
-
Hi, I am trying to build an n-tier architecture for my project. At present this is what I have: There is one Solutioin which contains the following: 1) The client (WinForms) project has a reference to the BusinessLayer project. 2) BusinessLayer project has a reference to the WebService 3) WebService has a reference to the DataLayer project. 4) DataLayer project calls the sql server. Would you say if I call the webservice direct from the client (WinForms) then this is a good idea or do you think the above 4 steps construct a good design? Thanks
-
Hi, I am trying to build an n-tier architecture for my project. At present this is what I have: There is one Solutioin which contains the following: 1) The client (WinForms) project has a reference to the BusinessLayer project. 2) BusinessLayer project has a reference to the WebService 3) WebService has a reference to the DataLayer project. 4) DataLayer project calls the sql server. Would you say if I call the webservice direct from the client (WinForms) then this is a good idea or do you think the above 4 steps construct a good design? Thanks
I'm in the process of architecting (and building) a similar sort of application. However, I see my WinForms client (and in the future a web or other type of client) simply as a presentation and controller layer - i.e. something that displays information to the end user and forwards the end user's intentions to the rest of the application. IOW, my WinForms client is extremely dumb and thin. (Unlike me - I'm just dumb). My webservice interacts with a business layer which in turn interacts with a data layer. The data layer serializes the data portion of several business objects that eventually find their way across the wire to the client (for display purposes). I've built an automated test harness at each layer - viz: object persistence, business logic, and web service. When I finally get around to building the GUI I'll farm out the visual testing to another party. Hope this helps. /ravi
This is your brain on Celcius Home | Music | Articles | Freeware | Trips ravib(at)ravib(dot)com
-
Hi, I am trying to build an n-tier architecture for my project. At present this is what I have: There is one Solutioin which contains the following: 1) The client (WinForms) project has a reference to the BusinessLayer project. 2) BusinessLayer project has a reference to the WebService 3) WebService has a reference to the DataLayer project. 4) DataLayer project calls the sql server. Would you say if I call the webservice direct from the client (WinForms) then this is a good idea or do you think the above 4 steps construct a good design? Thanks
Hi, I think that the n-tier architecture is appropriate. But if you call the webservice from the client tier, the n-tier model loses his sense... Because I supose that client tier contains only forms with events and this events call in few lines single methods from the below tier without applying bussines rules... It's only my point of view...
-
Hi, I am trying to build an n-tier architecture for my project. At present this is what I have: There is one Solutioin which contains the following: 1) The client (WinForms) project has a reference to the BusinessLayer project. 2) BusinessLayer project has a reference to the WebService 3) WebService has a reference to the DataLayer project. 4) DataLayer project calls the sql server. Would you say if I call the webservice direct from the client (WinForms) then this is a good idea or do you think the above 4 steps construct a good design? Thanks
Right now I am doing a Project with the following Layout: - A Database-Layer doing O/R mapping to the Database(es). - A Business-Logic doing calculations of the data from the Database(es) - A Webservice-Layer sending this computed data to and from the Client - A Client (mixed C++/C#) formatting the data for display and collecting the users input. The Client then calls the relevant Webservices to make the user-interactions happen. The goal is to have a system that ist capable to run on one (decent) PC of being separated into front- and backend, where the backend is a big machine and the client may be an older notebook or something.. The Client calls the Webservices directly, to get fresh data or to get calculations done. I hope this helps you to decide for one architecture or another.
"We trained hard, but it seemed that every time we were beginning to form up into teams we would be reorganised. I was to learn later in life that we tend to meet any new situation by reorganising: and a wonderful method it can be for creating the illusion of progress, while producing confusion, inefficiency and demoralisation." -- Caius Petronius, Roman Consul, 66 A.D.