Code Comments

Programming Forum and web based access to our favorite programming groups.
For Programmers: Free Programming Magazines | New: Database administration forum
Registration is free! Edit your profileCalendarFind other membersFrequently Asked QuestionsSearch -> 
Post New Thread











Thread
Author

Organizing Large Web Service
Hi all,

How do you all organize your large web services?

I have a service which needs to cover multiple components. Do you build one
asmx file for all the functions. Multiple ASMX files - grouping by
functionality? Or have do you go the document route - in which the details
are in the XML, and the web service routes it to the appropriate backend?

Some of the components need "high" performance, and I need usability, so
I'm hoping to stay away from the document-centric model.

Any ideas?

Thanks!


--
spamhoneypot@rogers.com (Do not e-mail)

Report this thread to moderator Post Follow-up to this message
Old Post
Spam Catcher
04-18-08 03:43 AM


Re: Organizing Large Web Service
One of the good things about webservices is that you can offset load between
servers easily based on functional requirement.  Given the opportunity, its
easy to treat a set of services as a component and dedicate hardware to it,
of course if they need to call other webservices in a chain this can impact
performance.  There is though no reason why you can't have lots of asmx file
locally utilising each others services though, nor is there really any
reason why you can't have one asmx file with lots of methods in it.

I tend to have lost of asmx file with related methods encapsulated and
offset these to other servers if the load in any single asmx method might
cause bottlenecks.

--
--
Regards

John Timney (MVP)
http://www.johntimney.com
http://www.johntimney.com/blog


"Spam Catcher" <spamhoneypot@rogers.com> wrote in message
 news:Xns9A83D222D526Busenethoneypotroger
s@127.0.0.1...
> Hi all,
>
> How do you all organize your large web services?
>
> I have a service which needs to cover multiple components. Do you build
> one
> asmx file for all the functions. Multiple ASMX files - grouping by
> functionality? Or have do you go the document route - in which the details
> are in the XML, and the web service routes it to the appropriate backend?
>
> Some of the components need "high" performance, and I need usability, so
> I'm hoping to stay away from the document-centric model.
>
> Any ideas?
>
> Thanks!
>
>
> --
> spamhoneypot@rogers.com (Do not e-mail)



Report this thread to moderator Post Follow-up to this message
Old Post
John Timney \(MVP\)
04-18-08 10:06 AM


Sponsored Links




Last Thread Next Thread Next
Search this forum -> 
Post New Thread

ASP .NET archive

Show a Printable Version Send to friend Email This Page to Someone! subscribe to this thread Receive updates to this thread
Computer Consultants
Programming Jobs
Visual Basic Controls
SQL Server Programming
Webservices
Java Security
Visual Studio
C# Programming
Visual J++
Software engineering
Open source Software
Perl Programming
PHP Programming
ASP Programming
ASP .NET Programming
Visual Basic Programming
Windows Scripting Host
Java Programming
Java Help
Java Beans
VBScript
Cobol
MAC Applications
Unix Programming
Forum Jump:
All times are GMT. The time now is 07:20 PM.

 
Free MCSE Braindumps | Real Estate Topics

Programming forum archive

Copyrights CodeComments.com 2004 - 2006

Powered by vBulletin Copyright 2000-2006 Jelsoft Enterprises Limited.