Wanted: .NET Infrastructure book

  • Thread starter Thread starter froowstie
  • Start date Start date
F

froowstie

Hi folks,

I work in IT, but on the infrastructure/engineering side. At work I'm now
being asked to design infrastructure solutions to support new .NET
applications. Typically, this infrastructure must be highly available and
support things like load balancing etc.... the only problem is I don't have
a thorough understanding of how to accomplish this. Is the infrastructure
tiered? How does the presentation layer talk to the middleware? These are
the types of questions I have.

I want to get a grounding how infrastructure wraps around the .NET framework
and how enterprise solutions are designed. Can anyone point me in the right
direction? eg... a good book or the like.

cheers, froowstie
 
Hi folks,
I work in IT, but on the infrastructure/engineering side. At work I'm
now being asked to design infrastructure solutions to support new .NET
applications. Typically, this infrastructure must be highly available
and support things like load balancing etc.... the only problem is I
don't have a thorough understanding of how to accomplish this. Is the
infrastructure tiered? How does the presentation layer talk to the
middleware? These are the types of questions I have.

I want to get a grounding how infrastructure wraps around the .NET
framework and how enterprise solutions are designed. Can anyone point
me in the right direction? eg... a good book or the like.
Click to expand...


You are not going to get a single answer. Each program you work with may
use a different architecture. Think of .NET similar to JAVA, WIN32 API, MFC,
or VB6/C++ applications that you currently support. It is the framework that
enables people to program against it. It is not an architecture that dictates
how one must build their applications in terms of x number of tiers, etc.
Dotnet is not an application (like BizTalk, Exchange, SQL Server, etc.)

Jim Wooley
http://devauthority.com/blogs/jwooley/default.asp
 
There's no way to tell.
I've seen a lot of .NET apps that are written so that they have all the
logic on the client side and then they just connect to the DB server (thick
client approach). I've seen them distributed so that different tiers are on
different servers (n-tier). You're going to have to ask some folks about
how they're going to be implementing .NET solutions...whether they're
web-based, client/server, whether they'll need an application server, etc.
There's no way to tell how the developers are going to build the application.

Then from a management side, how these servers will be managed
(MOM/SMS/Application Server, etc)
 
Back
Top