Architecture question

[Lomax]

Hi !

I have to develop an accounting soft solution. For many reasons we decided
to use a three tier architecture. The logical tier is composed of logical
components and a web service facade that delegate to the logical components.
The presentation will be composed of both a widows forms application and a
web forms application. Both applications will access the web service facade
either through Internet or an intarnet. Of course, an accounting software
solution will have a HUGE quantity of datas to be transfered to the
presentation layer...

My question is: are web services a good way to implement the facade of the
business layer ?? Will it be ok to transfer huge amount of datas to the
presentation tier ?? If no, how would you design such an architecture ??

Thanks for any help !!

[John Bailo]

Lomax wrote:

Hi !

I have to develop an accounting soft solution. For many reasons we decided
to use a three tier architecture. The logical tier is composed of logical
components and a web service facade that delegate to the logical components.
The presentation will be composed of both a widows forms application and a
web forms application. Both applications will access the web service facade
either through Internet or an intarnet. Of course, an accounting software
solution will have a HUGE quantity of datas to be transfered to the
presentation layer...

My question is: are web services a good way to implement the facade of the
business layer ?? Will it be ok to transfer huge amount of datas to the
presentation tier ?? If no, how would you design such an architecture ??

Thanks for any help !!

Well, in some sense, the solution should not necessarily transfer 'huge'
amounts of data to the UI. The whole point of having an intermediary
layer is to translate UI selections, to business logic, which then deals
with the large volumes of data.

So, you should think in terms of a lot of very specific and refined web
services that accomplish discrete tasks. These services should do the
work of creating the big queries and updates and insulate the user from
dealing with dumping full tables into the UI.
--
http://antimeme.texeme.com