Re: Scalability questions....

These are my rules of thumb:

1. Hardware code is faster than software code (i.e. hardware SSL is faster than software SSL).
2. Use best practices starting at the server layer.
3. Don't rely on sticky sessions. Each client should be able to be serviced by a different server on each roundtrip.
4. Make the calls as much as pass-through as possible.
5. Use caching where possible.
6. Do load testing.

BTW, SQL Server can handle many users if setup correctly. I worked for a company that hosted WinAmp for a month back in the dotcom days. We averaged 60 MB/sec of bandwidth and used SQL Server to log and analyze the downloads.

Bryan Phillips
MCSD, MCDBA, MCSE
Blog: http://bphillips76.spaces.live.com




"smerf" <smerf@xxxxxxxxxx> wrote in message news:Rab1h.11073$Fd7.2513@xxxxxxxxxxxxxxxxxxxxxx:

For the sake of argument, let's say I wrote an application that made
extensive use of web services. And, again for the sake of argument, let's
assume that the app became very popular and millions around the globe used
it daily.

I know how to write a webservice attached to a backend database for use by a
few people. But how do I write a data intensive webservice that can be
scaled to service thousands or millions of people?

How do you code in scalability? How do you scale up a webservice from a
single, hosted webserver to whatever it takes to handle thousands of
simultaneous requests? Do you add more webservers? If so, how and how do
they all service the same address?

As for the SQL Server backend... How do you scale the SQL Server backend to
handle millions of requests for such a webservice? There must be a limit to
the simultaneous requests a single instance of SQL server can handle - so
how do handle going from 50 users online to 500,000 users online?

I want to build an app for use online, but I don't want to box myself in -
just in case.....

--
Smerf
"Better to understand a little than to misunderstand a lot."

.

Relevant Pages

  • Re: ThreadAbort Exceptions !! HELP !!
    ... Well we checked for queued requests last night and there were none during ... Looks like our SQL server box is ... trace seems to usually point at a webservice not an aspx page. ... System.Threading.WaitHandle.WaitOne(Int32 millisecondsTimeout, Boolean ...
    (microsoft.public.dotnet.framework.webservices)
  • RE: Webservice can not connect to Sql server 2000
    ... Windows service pack. ... All i am dong is trying to open a connection from a .Net webservice (using ... IIS installed on it and connecting to the sql server which is running on ...
    (microsoft.public.sqlserver.connect)
  • Proxy Authentication error when calling a webservice from SQL2K stored proc
    ... I'm performing a webservice call from a SQL Server stored proc. ... Authentication Required.' ...
    (microsoft.public.sqlserver.programming)
  • Re: Login failed for user NT AUTHORITYANONYMOUS LOGON
    ... Is the SQL server box in the same domain as the web server (or do they have ... went wrong with your impersonation. ... > I have a local webservice and I was to use to access a SQL server on their ... > of the domain user in the web.config. ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Debugging HTTP 500 errors
    ... frequently the IIS log shows a status 500 being returned to the ... Webservice protected using basic authentication. ... SQL Server 2000 with the latest service pack and updates. ...
    (microsoft.public.dotnet.framework.aspnet.webservices)
Loading