Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / Web Services / March 2005

Tip: Looking for answers? Try searching our database.

Webservice farm, what's best practice??

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
S?ren M. Olesen - 02 Mar 2005 08:07 GMT
Hi

What's best practice for distributing the load between webservices on
different computers? What I'd like is for a client to always select the
webservice with the least load, I.e. If one is idle then that one should be
selected, otherwise one working on a job with less priority than mine should
be selected and the job currently running should be paused.

Is there a pattern/best practice for doing this??

TIA

S?ren
MasterGaurav - 02 Mar 2005 13:49 GMT
In a web-farm, the load-balancer should do it for you (load part).

However, if priority comes into picture, you may need to have your own
load-balancer which proxies in front of the web-service-farm.

Not sure if anything is available out-of-the-box.

--
Cheers,
Gaurav Vaish
http://www.mastergaurav.org
http://mastergaurav.blogspot.com
--------------------------------
Dilip Krishnan - 02 Mar 2005 15:19 GMT
Hello Søren,
   Essentially if you want a software load balancer you would need to consider
FrontController pattern in .net. Having said that, I'd say there is a lot
of things you need to think about when you decide to do this. Things that
jump to mind are how do you pass along credentials for authentication and
authorization to the balanced endpoints?  Its possible but rather tedious
to have jobs created executed and paused based on priority in web service
land. What you need to consider for doing something thats more task oriented
is create a windows service. IMO, you could create a non-loadbalanced web
service that sends requests to a queue and have a windows service that picks
tasks and allocates tasks to worker threads that you can now control and
prioritize

HTH
Regards,
Dilip Krishnan
MCAD, MCSD.net
dkrishnan at geniant dot com
http://www.geniant.com

> Hi
>
[quoted text clipped - 10 lines]
>
> Søren

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.