RE: Business Layer - Application Server

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hello macfarmw,

The idea u suggest is too hazardous. I can't see the reason to keep ASP.NET and data on the same machine due to security violation
Server with WEB should be located separately, and all interactions with business logic are on the COM+/Remoting calls.

m> If your client program is an asp.net web site and your databases are
m> on the local network then I see no advantage to a separate
m> application server unless you doing something extreme and need the
m> additional cpu. We put our business logic into components that are
m> deployed with the website.
m> m> If the clients are Windows apps then it can be a good idea do put the
m> business objects on an app server and connect the clients using Web
m> Services, .Net Remoting, or Enterprise Services. This allows you to
m> upgrade the server portion without redeploying the clients as long as
m> you don't make a breaking change.
m> m> Any kind of remote access is going to be slower because of the
m> overhead but can be well worth it because of redeployment savings.
m> m> Matthew
m> m> "Robert" wrote:
m>
Hardware setup of 3 servers.
1) Web Server - DMZ
2) Application Server - Local Intranet
3) Database Server - Local Intranet
The main question I have is where should I put my business layer,
physical
location, for my web application? The initial thought was to have the
business layer reside on the application server, but from reading
articles
and posts, it appears that there is a performance hit. Is there any
real
benefit to having a physical application server? Should I use the
App_Code
folder or remoting (application server)? Are there performance
comparisons
between having the classes reside on the web server vs. the app
server? Is
there any reason to use Web Services on the Application server if we
are not
exposing the service to the Internet?
Thanks in advance

---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/laflour

"At times one remains faithful to a cause only because its opponents do not cease to be insipid." (c) Friedrich Nietzsche


.

Relevant Pages

  • Re: why have a server?...advice needed
    ... For 20-22 users and 30 machines, with a QUALIFIED IT Consultant, that amounts to about 5-12 hours per month of IT support and in my opinion, if the network is installed properly with little change other than adding a computer and a user periodically, there should be no real need for more. ... Had I charged them my full $150/hour rate, I believe they would have been billed a total of roughly $10,000 last year, and that includes an emergency rebuild/replacement of their server when the old hardware died. ... I don't know what the IT costs are or what the EXACT business needs you have are, but from what I'm understanding, I don't think the IT support costs should be more than what I stated above. ... At one of my clients, they are packed in like sardines and by redirecting their folders, they can sit at ANY unused computer and when they log on, they have complete access to all their files without having to do anything. ...
    (microsoft.public.windows.server.general)
  • Re: How many years to change server? and why?
    ... SuperGumby [SBS MVP] wrote: ... You replace things when the business case justifies it. ... I'm an oddball in that I have clients running (SHOCK!!! ... In fact, with Virtualization abilities growing, it might make a LOT of sense to start setting up all systems on Hyper-V in Server 2008. ...
    (microsoft.public.windows.server.sbs)
  • Re: Tagging interfaces
    ... In order for the server to pass the correct stuff to specific interested ... clients the business part of the server must keep references to its clients. ... and also a Location reference. ...
    (comp.lang.java.programmer)
  • Re: SBS2003 Partitioning
    ... It doesn't matter how small the business is it is a bad practice to sell a workstation for use as a server. ... Businesses come to rely on a server very quickly and within a matter of months may no longer be able to function effectively if the server goes down. ... There is no real advantage to moving the page file from the system partition in a small server with one drive/array, and yes it's a good idea to keep Exchange and SQL on separate partitions but given the size of drive you intend on using probably two partitions, at most three, is your best option. ...
    (microsoft.public.windows.server.sbs)
  • Re: Is a server really needed?
    ... to a business of 100 and it makes sense. ... server environments. ... use for production and learning, and it means that you can build a SBS ... you are doing your clients a disservice. ...
    (microsoft.public.windows.server.sbs)