N Layered Domain Oriented Architecture Guide With .NET 4.0
User Manual:
Open the PDF directly: View PDF
Page Count: 475 [warning: Documents this large are best viewed by clicking the View PDF Link!]
- This book is dedicated to…
- Contents
- Prologues
- .Net Architecture Guide Introduction
- The Architecture Design Process
- N-Layered Architecture
- 1.- N-Layered applications architecture
- 2.- DDD N-Layered architecture style
- 2.1.- Presentation, Application, Domain and Infrastructure Layers
- 2.2.- Domain Oriented N-Layered Architecture
- 2.3.- De-coupling between Components
- 2.4.- Dependency Injection and Inversion of control
- 2.5.- Modules
- 2.6.- Model Subdivision and Work Context
- 2.7.- Bounded Contexts
- 2.8.- Relations between Contexts
- 2.9.- Implementation of Bounded Contexts in .NET
- 2.10.- Mapping technologies in N-Layered Architecture
- 2.11.- Implementing a Layered Architecture in Visual Studio 2010
- 2.12.- Sample application of N-Layer DDD with .NET 4.0
- 2.13.- Visual Studio Solution Design
- 2.14.- Application Architecture with Layer Diagram of VS.2010
- 2.15.- Implementation of the Dependencies Injection and IoC with UNITY
- 2.15.1.- Introduction to Unity
- 2.15.2.- Usual scenarios with Unity
- 2.15.3.- Main Patterns
- 2.15.4.- Main methods
- 2.15.5.- Registering Types in the Unity Container
- 2.15.6.- Dependency Injection in the Constructor
- 2.15.7.- Property Injection (Property Setter)
- 2.15.8.- Summary of the Main Features of Unity
- 2.15.9.- When to use Unity
- 3.- EDA (Event Driven Architecture)
- 4.- Dual access to data sources
- 5.- Physical tiers (Tiers) deployment
- Data Persistence Infrastructure Layer
- 1.- Data persistence infrastructure layer
- 2.- Logical design and architecture of the data persistence layer
- 3.- Testing in the data persistence infrastructure layer
- 4.- Data access design considerations
- 5.- Implementing data persistence layer with .Net 4.0 and Entity Framework 4.0
- 5.1.- Technology Options for the Data Persistence Layer
- 5.2.- Entity Framework Possibilities in the Persistence Layer
- 5.3.- Domain Entity options using Entity Framework
- 5.4.- Creation of the Entity Data Model
- 5.5.- T4 Templates of POCO/Self-Tracking Entities generation
- 5.6.- EF ‘Self-Tracking Entities’
- 5.7.- Moving Entities to the Domain Layer
- 5.8.- Data Persistence T4 Templates and Data Source Connection
- 5.9.- Implementing Repositories using Entity Framework and LINQ to Entities
- 5.10.- Repository Pattern Implementation
- 5.11.- Unit Testing and Repository Integration Implementation
- 5.12.- Data Source Connections
- 5.13.- Strategies for Data Source Error Handling
- 5.14.- External Service Agents (Optional)
- 5.15.- References of Data Access Technologies
- The Domain Model Layer
- 1.- The Domain
- 2.- Domain Layer: Logical design and architecture
- 3.- Implementing the domain layer with .NET 4.0 AND decoupling objects with unitY
- 3.1.- Implementing Domain Entities
- 3.2.- Generation of POCO/STE Entities with EF T4 Templates (Model First and Database First)
- 3.3.- ‘Code First’ approach for implementing POCO entity classes
- 3.4.- Domain Logic in Entity Classes
- 3.5.- Location of Repository Contracts/Interfaces in the Domain Layer
- 3.6.- Implementing Domain Services
- 3.7.- SPECIFICATION Pattern
- 3.8.- Implementing Unit Testing for the Domain Layer
- Application Layer
- 1.- Application layer
- 2.- Application layer logical design and architecture
- 3.- Application layer components
- 4.- Implementing the application Layer using .NET
- The Distributed Services Layer
- 1.- Location in the N-Layered architecture
- 2.- Service Oriented architectures and N-Layer architectures
- 3.- N-Layered Architecture relationship with Isolated Applications and SOA Services
- 4.- What is SOA?
- 5.- Internal architecture of the SOA services
- 6.- Design steps for the services layer
- 7.- Data object types to be Transfered
- 8.- Consumption of distributed services based on agents
- 9.- Interoperability
- 10.- Performance
- 11.- Asynchronous vs. Synchronous communication
- 12.- REST vs. SOAP
- 13.- Introduction to SOAP and WS-*
- 14.- WS-* specifications
- 15.- Introduction to rest
- 16.- ODATA: Open Data Protocol
- 17.- Global Design rules for SOA systems and services
- 18.- Implementing the distributed services layer with WCF 4.0
- 19.- Technological options
- 20.- introduction to WCF (Windows Communication Foundation)
- 21.- Implementation of WCF service layer in N-Layer architecture
- 22.- Types of data objects to communicate when using wcf services
- 23.- Publishing application and domain logic
- 24.- WCF service deployment and monitoring in Windows Server AppFabric (aka Dublin)
- 25.- serviceS and WCF global references
- Presentation Layer
- 1.- Situation in N-Layer architecture
- 2.- Requirement to invest in user interface
- 3.- The Need for architecture in the presentation layer
- 4.- Architecture patterns in the presentation layer
- 5.- Implementing the Presentation Layer
- 6.- data validation in the interface (WPF)
- 7.- implementING MVC with asp.net MVC
- Cross-Cutting Infrastructure layers
- 1.- Cross-cutting infrastructure layers
- 2.- Cross-cutting infrastructure LOCATION in the N-Layered architecture
- 3.- General design considerations
- 4.- Cross-cutting aspects
- 5.- Cross-cutting aspectS implementation using .NET
- Architecture and Patterns for PaaS Cloud-Computing and Windows Azure
- 1.- Application architecture in the cloud
- 2.- Architecture scenarios in the cloud
- 3.- Basic scenario: direct migration from on-premise application to the cloud
- 3.1.- Logical Architecture (Basic Scenario)
- 3.2.- Reasons for using Windows Azure
- 3.3.- Brief Introduction to the Windows Azure Platform
- 3.4.- Implementing of a Basic Scenario in Windows Azure Platform
- 3.5.- Steps to migrate the sample NLayerApp Application to Windows Azure (Basic Scenario in the Cloud)
- 3.5.1.- Migrating SQL Server Databases to SQL Azure
- 3.5.2.- Changing the ADO.NET EF Connection String
- 3.5.3.- Migrating Hosting Projects from IIS to Azure
- 3.5.4.- Deploying our Application in the Production Windows Azure Cloud (Internet)
- 3.5.5.- Web image management: Change from local storage (disk) to Windows Azure Blobs
- 3.5.6.- Windows Azure Security
- 3.5.7.- Other items to be considered when migrating applications to Windows Azure
- 4.- Advanced scenario: High scalable applications in Cloud-Computing
- Conclusions