3. User Interface LayerUser Interface Layer
Business LayerBusiness Layer
Data LayerData Layer
Object
Library
DatabaseDatabase
ExternalSystems
4. The solution does not lend its
self to being distributed across
load tolerant physical
architecture.
The separation of concerns
becomes blurred between the
layers making it hard and
expensive to maintain code.
Data has a tendency to be
leaked across the solution up to
the UI making many N-Tier
systems very vulnerable to
exploits such as Sql Injection
Attacks.
N-Tier models tend to result in
teams that have tier focused
developers who are not cross
skilled across layers.
5. User Interface LayerUser Interface Layer
Invoicing
Service
Invoicing
Service
Stock
Management
Service
Stock
Management
Service
Customer
Management
Service
Customer
Management
Service
Marketing
Service
Marketing
Service
Email ServiceEmail Service
Email ServiceEmail Service
Database , External Services, Ftp , SMTP etcDatabase , External Services, Ftp , SMTP etc
6. One Service One Concern
Highly Distributable
Load Tolerant ( WCF + MSMQ) .
Ask don’t Tell (Good
Encapsulation Of Concerns +
Request and Response Style
Messaging ).
Cheap to Maintain and Expand.
Lends them selves to
geographically distributed
infrastructure. (WAN of LAN’s).
Multiple Security Models
Available.
7. SOA + Message Bus
Invoicing
Service
Invoicing
Service
Stock
Management
Service
Stock
Management
Service
Customer
Management
Service
Customer
Management
Service
Marketing
Service
Marketing
Service
Email ServiceEmail Service
Email ServiceEmail Service
Message Bus and Bus Sub Systems
UI’s
8. Complete abstraction of Business
Services.
Load Balancing
High Performance
Fault Tolerant
Generic Messaging
High Through Put Of Transactions
Distributed Transaction
Management
9. Mass Transit
Mass Transit is an open source
project which implements an
architecture that is often extended
by software teams to provide
custom solutions.
Biztalk + ESB Tool Kits.
This is Microsoft’s enterprise
orchestration offering.