Maximizing.ASP.dot.NET.Real.World.ObjectOriented.Development [Electronic resources]

Jeffrey Putz

نسخه متنی -صفحه : 146/ 44

Chapter 4. Application Architecture

To this point in the book, we've explored the design and development of individual classes. These units of code enable you to encapsulate functionality into reusable components that perform some specific task. Naturally these parts will operate in the context of some bigger picturesome grand scheme that performs the greatest things ever. We refer to this scheme as the application architecture.

In this chapter we'll look at ways to split up your application into logical pieces and how your classes come together to do the greatest things ever.

In this chapter, we talk about layering and tiers. Technically, these are not the same thing, though they're frequently used interchangeably. A tier is often defined as a single machine or group of machines that share the responsibility in a bigger system. In fact, the Web browser is considered a tier of an application because it ultimately acts as the user interface. A layer refers more to the conceptual unit of an application, such as a data layer that includes the database.