-
as seen on ASP.net Weblogs
- Search for 'ASP.net Weblogs'
Three-tier (layer) is a client-server architecture in which the user
interface, business process (business rules) and data storage and data
access are developed and maintained as independent modules or most often
on separate platforms. Basically, there are 3 layers, tier 1
(presentation tier…
>>> More
-
as seen on Stack Overflow
- Search for 'Stack Overflow'
I have for some time build n-tier Applications using a database server as the data tier, Winforms as the presentation tier and an ASP.NET asmx webservice in the middle to send back and forth untyped Datasets. While this approach has worked for me so far, it certainly does feel outdated today.
What…
>>> More
-
as seen on Stack Overflow
- Search for 'Stack Overflow'
I would like some advice on the best approach to use in the following situation...
I will have a Windows Application and a Web Application (presentation layers), these will both access a common business layer. The business layer will look at a configuration file to find the name of the dll (data…
>>> More
-
as seen on Stack Overflow
- Search for 'Stack Overflow'
Hi,,,
I’m working on an application which has been designed using n-tire application architecture .The application was developed in the .NET platform utilizing C#,VB.NEt, Framework 3.5, Dataset, WCF, asp.net update panel, JavaScript ,Josn, 3rd Party tools.
my current proposed layout is such
presentation…
>>> More
-
as seen on Stack Overflow
- Search for 'Stack Overflow'
In an N-Tier app you're supposed to have a business logic layer and a data access layer.
Is it bad to simply have two assemblies: BusinessLogicLayer.dll and DataAccessLayer.dll to handle all this logic? How do you actually represent these layers. It seems silly, the way I've seen it, to have a BusinessLogic…
>>> More
-
as seen on DotNetBlocks
- Search for 'DotNetBlocks'
The three-tier client/server model is a network architectural approach currently used in modern networking. This approach divides a network in to three distinct components.
Three-Tier Client/Server Model Components
Client Component
Server Component
Database Component
The Client Component…
>>> More
-
as seen on Programmers
- Search for 'Programmers'
I am developing a web based application whose primary objective is to fetch data from the database, display it on the UI, take in user inputs and write them back to the database. The application is not going to be doing any industrial strength algorithm crunching, but will be receiving a very high…
>>> More
-
as seen on Programmers
- Search for 'Programmers'
I was attempting to find a best practice for modeling the tiers in a Java EE application yesterday and couldn't come up with anything current. In the past, say java 1.4, it was four tiers:
Presentation Tier
Web Tier
Business Logic Tier
DAL (Data Access Layer ) which I always considered a tier and…
>>> More
-
as seen on Server Fault
- Search for 'Server Fault'
Imagine I have an n-tier architecture in an auto-scaled cloud environment with say:
a load balancer in a failover pair
reverse proxy tier
web app tier
db tier
Each tier needs to connect to the instances in the tier below.
What are the standard ways of connecting tiers to make them resilient to…
>>> More
-
as seen on Geeks with Blogs
- Search for 'Geeks with Blogs'
Recently the question came up from a close friend of mine, "will my PhD help me attain a higher income in the north west?" I had to tell him, that it might get him a little more, but it won't get him in the top income brackets for the occupation. Another time, a few days later, someone else asked…
>>> More
