Re: Current approach to fast n tier oracle design

Fletcher,

Fair enough, if there is a real need for web services then it's justified to
use them. Enable the Zip compression on the webservice to reduce the network
load, google for it there are loads of examples. Also enable as much caching
as you can get away with. Just remember that the clients attacking your
webservice will not be using zip compression by default. You will have to
enforce the use of it.

For the record, when I do specifications I find out what is best for the
client, if that means .Net/Java/Lamp: Client - Server, N-Tier , Webservices
or Web apps then that is what I sugest. But I find a lot of people make
discisions not on what is best but what will get them promoted faster, and
that is usually internal web applications that look nice and flashy with the
latest buzz-words but barely fill the needs of the end user.

One client thought that demanding 1,000,000 records to be sent via a
webservice and have a response time of <200ms was a valid criteria, and it
had to use webservice, Silverlight, ajax and have all the shortcut keys
associated with a word document.

Dave,



On Mon, Feb 2, 2009 at 7:09 PM, Fletcher's Discussion Account <
[email protected]> wrote:

> Dave,
>
> You have some good points and I will look into the binary mode of wcf.
>  But,
> in this case, there is at least one other desktop application (beside the
> one I am rewriting) that will probably use the web service.
>
> The initial plan calls for using a web page to communicate with the user
> (vs. a desktop app currently in use.)  As the queries results are generally
> small, I am hoping that the response time won't be too bad.
>
> One thing I have found with MS is that they try to come up with some things
> to make life easier for developers, but they often tend to be so
> comprehensive that their performance is pitiful.
>
> I know I can test all this stuff, but I was hoping that some of you have
> played with these and either know some tweaks that might make a difference
> or if there is a variation on approach that I might use.
>
> I do know that I could write everything on my own, using really tight code
> that just talked directly to the data, etc.  But part of the goal is to
> write code that can be managed by other .NET developers, so I would like to
> use "standard" approaches where possible.
>
> Thanks,
>
> Fletcher
>

===================================
View archives and manage your subscription(s) at http://peach.ease.lsoft.com/archives