Domain Driven Design (DDD) is an object-oriented approach to designing software based on the business domain, its elements and behaviors, and the relationships between them. It aims to enable software systems that are a realization of an underlying business domain by defining a domain model expressed in the language of business domain experts. The domain model can be viewed as a framework from
which solutions can then be rationalized.
Monday, January 10, 2000
Saturday, January 1, 2000
Why .NET 3-tier architect or n-tier architect?
The main benefits of the N-tier/3-tier architectural style are:
+ Maintainability: Because each tier is independent of the other tiers, updates or changes can be carried out without affecting the application as a whole.
+ Scalability: Because tiers are based on the deployment of layers, scaling out an application is reasonably straightforward.
+ Flexibility: Because each tier can be managed or scaled independently, flexibility is increased.
+ Availability: Applications can exploit the modular architecture of enabling systems using easily scalable components, which increases availability.
+ Maintainability: Because each tier is independent of the other tiers, updates or changes can be carried out without affecting the application as a whole.
+ Scalability: Because tiers are based on the deployment of layers, scaling out an application is reasonably straightforward.
+ Flexibility: Because each tier can be managed or scaled independently, flexibility is increased.
+ Availability: Applications can exploit the modular architecture of enabling systems using easily scalable components, which increases availability.
Subscribe to:
Posts (Atom)