Re: middle tier recommendations
From: Nick Malik (nickmalik_at_hotmail.nospam.com)
Date: 11/25/04
- Previous message: artmanaged33_at_newsgroup.nospam: "IP-adress of connecting peer when using remoting over HTTP in IIS"
- In reply to: Param R.: "middle tier recommendations"
- Next in thread: Param R.: "Re: middle tier recommendations"
- Reply: Param R.: "Re: middle tier recommendations"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 25 Nov 2004 19:53:09 GMT
What is driving the architecture? What are the key constraints?
Honestly, most applications are fine with an ASP.NET layer that calls a
simple middle layer, written as DLLs, that call SQL. That said, most
applications have fewer than 100 concurrent users. I'm going to venture a
guess that this doesn't apply to you.
How many servers have you set aside for this application?
How many users do you plan to serve with this application?
What is the nature of their use (continuous use for business day, occasional
light use, occasional heavy use, receiving a stream of information)?
In addition, you didn't provide the key constraints that drives the
architecture.
Do you have high uptime requirements (99.9% or better)?
Do you have variable scalability issues (sudden spikes that increase traffic
by an order of magnitude or more for a sustained period)?
Do you need to be able to modify the behavior of the system while it is
running due to the nature of competition in your business?
Do you have existing systems that you need to communicate with? If so, are
these systems designed for real-time communication or do you need to batch
things up?
Without at least a little of this information, my answer would be too vague
to be useful.
As for .NET remoting, it is a useful mechanism for designs that need to
partition the execution of the application onto multiple servers. The
marshalling is far more efficient than with web services, but it is still
marshalling... and if you are sending data sets across a marshalling
boundary, you are probably not designing your interfaces correctly.
An excellent book: Advanced .NET Remoting by Ingo Rammer.
HTH,
---- Nick
"Param R." <pr@nospam.com> wrote in message
news:%23kiwNQj0EHA.804@TK2MSFTNGP12.phx.gbl...
> Hi all, we are in the process of architecting a new application that will
> have an asp.net front end & sql back end. In the past we have used
> webservices as a middle tier solution but in terms of performance it has
not
> been upto the mark. Besides with the latest .net version there are some
> known issues with calling web services (keepalives etc.). What other
middle
> tier solution does .net have to offer? What is .net remoting and how does
it
> work? Is it similar to DCOM? Does it have to run under IIS? I would like
> something that is not dependent on IIS preferably. In our solution we will
> be passing custom objects back and forth with the middle tier interacting
> with the database.
>
> Any help and guidance here is much appreciated!
>
> thanks!
>
>
- Previous message: artmanaged33_at_newsgroup.nospam: "IP-adress of connecting peer when using remoting over HTTP in IIS"
- In reply to: Param R.: "middle tier recommendations"
- Next in thread: Param R.: "Re: middle tier recommendations"
- Reply: Param R.: "Re: middle tier recommendations"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|