Architecture_v3

Architecture_v3

Patterns used:

Model View Controller:

• Because the is the best pattern in terms of managing the front-end's behave with data management

N-Tier:

• Separation of concerns; Multiple layers handle different functionality e.g repository handles access to the database
• Code management; Code is much more easier to maintain and management.
• Agile: Different people can work on different parts of the code base without tripping over each other.

Broker

• Used to connect the backend and front end.
• Provides a single point for service access.
• Connects the database and services layer.
• Provides a single point of entry for database access.