<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>N-Tier on Karpoke - Just Another Blog</title><link>http://karpoke.ignaciocano.com/tags/n-tier/</link><description>Recent content in N-Tier on Karpoke - Just Another Blog</description><generator>Hugo -- 0.167.0</generator><language>es</language><lastBuildDate>Tue, 31 Jul 2012 14:54:00 +0100</lastBuildDate><atom:link href="http://karpoke.ignaciocano.com/tags/n-tier/index.xml" rel="self" type="application/rss+xml"/><item><title>N-Tier Architecture And Tips</title><link>http://karpoke.ignaciocano.com/2012/07/31/n-tier-architecture-and-tips/</link><pubDate>Tue, 31 Jul 2012 14:54:00 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2012/07/31/n-tier-architecture-and-tips/</guid><description>&lt;blockquote&gt;
&lt;p&gt;N-Tier architecture is an industry-proved software architecture model,
suitable to support enterprise-level client/server applications by
resolving issues like scalability, security, fault tolerance and etc.
.NET has many tools and features, but .NET doesn’t have pre-defined
ways to guard how to implement N-Tier architecture. Therefore, in
order to achieve good design and implementation of N-Tier architecture
in .NET, understanding fully its concepts is very important. However,
many of us may hear, read or use N-Tier architecture for many years
but still misunderstand its concepts more or less. This article tries
to clarify many basic concepts in N-Tier architecture from all
aspects, and also provide some practical tips. The tips in this
article are based on the assumption that a team has a full control
over all layers of the N-Tier architecture.&lt;/p&gt;
&lt;/blockquote&gt;</description></item></channel></rss>