Com+ vs IIS vs StandAlone

As im sure most of you are aware of you can not host .Net services without
IIS. This where my question comes in on what is the best practice on objects
that you know will have to scale. With my understanding of .Net, if you host
the process directly from a service, then every hit to the object is going
to create a new object.. So if your getting 100,000 hits per minute (i know
this is high but im using it as an example) then there will be 100,000
objects created and destroyed. I assuming if i didn't work like this then it
would be like apartment threading and only one call could happen at a time
and there would be blocking. A lot of these objects will be in memory at the
same time. Is my understanding of how things work lax or is this really is
what going to happen? I would assume this would scale really poorly. This
example could be a web service or say something you exposed with WCF.

My understanding of how IIS works is very limited. I'm sure that IIS has
some time of redudancy threading to help the situation above. Am i right or
am i wrong? So if you host under IIS would it scale any better?

Last comes com+. Which has facilities like object pooling & connection
pooling and ect that i would think would allow these services to scale the
best. Am i wrong?

So i guess the overall question is what is the differences between how each
of these solutions would scale? Which solution would be the best? Would
there big a big difference

For simplicity lets leave server farms and clustering out of this.

Any help would be appreciated.

thanks,
Brent


.

Relevant Pages

  • Standalone vs IIS vs COM+?
    ... As im sure most of you are aware of you can not host .Net services without ... I would assume this would scale really poorly. ... My understanding of how IIS works is very limited. ...
    (microsoft.public.dotnet.general)
  • experiment supports concept of using host header names as securit y layer
    ... ISAPI filters can't evaluate a request until a virtual site has been ... selected and its set of running ISAPI filters has become known to the IIS ... As a quick experiment in using a host header name as a security device, ...
    (Focus-Microsoft)
  • Re: how to configure host headers for 3 IIS machines ?
    ... If you only have one public IP, this will not work with IIS only. ... Host multiple websites on one machine, and distinguish them with a host ... Using host headers, without including the external IP and another port is ... > Im looking to run three IIS machines on the same public IP. ...
    (microsoft.public.inetserver.iis)
  • Re: how to configure host headers for 3 IIS machines ?
    ... The CS-Host field is sent by the client. ... If the server is configured with host headers only, ... Kristofer Gafvert - IIS MVP ...
    (microsoft.public.inetserver.iis)
  • Re: Multiple domains
    ... I was simply clarifying that IIS won't host an "almost ... Yes, it can be done, using host headers in IIS. ... He is however limited to one secure site, ...
    (microsoft.public.windows.server.dns)