The most common architecture pattern is the layered architecture pattern, otherwise known as the n-tier architecture pattern. This pattern is the de facto standard for most applications and therefore is widely known by most architects, designers, and developers. The layered architecture pattern closely matches the traditional IT communication and organizational structures found in most companies, making it a natural choice for most business application development efforts.

1. Layered Software Architecture
23th May 2018
Thang Nguyen – Chief Technology Officer

2. 2
Content
1 Logical Layer Architecture
2 Physical Tier Architecture
3 Comparative
4 Summary
5 Questions

3. 3
CONTENT
Logical Layered Architecture

4. 4
1960sand1970s

5. 5
1980sand1990s

6. 6
1990s

7. 7
Logical Layered Architecture

8. 8
Presentation Layer
• Also known as Frontend Layer, User Interface Layer
• Responsible for creating and displaying the user interface and handling user
interaction
• Data shown is fetched from the Domain Layer

9. 9
Service Layer
• Also known as Web Service Layer
• Responsible for exposing a web service, api and returning the method result
as XML, JSON, Binary data…
• Data returned is retrieved from the Domain Layer

10. 10
DomainLayer
• Also known as Business Layer
• Responsible for all the business logic in the application
• Consists of a Domain Model and Domain Service

11. 11
DomainModel
• Also known as Business Model, Business Objects, Entities…
• Responsible for having a model that reflects how the business stakeholders
look at the world
• Consists of entities with relationships and behavior
• Similar to a database model but a domain model is richer

12. 12
DomainService
• Also known as Business Service, Business Manager…
• Business Logic that does not belong within an entity

13. 13
Infrastructure Layer
• Also known as Data Access Layer, Repository Layer…
• Responsible for querying a database, calling a web service, api, sending
email, sms …

14. 14
Sample
• We want to create a task management application with employees and
related tasks. A task consist of an id, a task name, a deadline, a finished
time. An employee can be assigned many tasks and we want to check task
progress completed or miss deadline.
• Technology: .NET, ASP.NET MVC

15. 15
Sample Domain Model

16. 16
Sample Domain Model

17. 17
Sample
Infrastructure

18. 18
Sample
Infrastructure

19. 19
Sample
Domain Service

20. 20
Sample
Show result to the user

21. 21
Whyshould youhavemanylayers
• Independence
• More secure
• Reusability
• Reusing components easily
• Increase flexibility, maintainability, and scalability

22. 22
Layer architecture disadvantages
• Sometimes difficult to cleanly assign functionality to the “right” layer
• Can’t be used for simple application because it adds complexity

23. 23
CONTENT
Physical Tier Architecture

24. 24
Architecture components
• Architecture components of any system is “software” and “hardware”
• Software is programs and other operating information used by computer
• Hardware is the machines, wiring, and other physical components of a
computer or other electronic system.

25. 25
Componentsof hardware
Client
Server
Network

26. 26
2 –Tier windowsclient architecture

27. 27
3 –Tier windowsclient architecture

28. 28
3 –Tier web architecture

29. 29
4 –Tier architecture

30. 30
Whyhavemanytiers
• Reuse logic across applications
• Improve security, e.g. restrict database access for the client by going
through a service
• Improved performance, the performance critical tiers can be scaled across
multiple servers

31. 31
CONTENT
Summary

32. 32
Summary
• Logical Layers
– How you logically divide the code in application
– Three layers architecture is most common
• Presentation Layer
• Domain Layer with a Domain Model and Domain Service
• Infrastructure Layer for communicating with data source
• Physical Tiers
– How you divide the application into many sub-applications

33. THANK YOU
FORLISTENING