A database persistently stores an information system’s data. Backend actions commonly retrieve, insert, update, or delete that information, making the backend strongly database-centric. section 1.4
A database participates in a larger backend architecture:
- A frontend sends requests to the backend. section 1.4
- Controllers convert requests into commands for the domain model, which applies business rules. section 1.4
- Repositories contain retrieval and persistence logic and communicate with the database behind the scenes. section 1.4
- External systems and APIs can exchange information with the backend while the database remains its central store. section 1.5
Training-management application
A training platform stores employees, courses, trainers, enrollments, and reports in its database. Its backend retrieves and changes these records, while APIs and a frontend provide access to the functionality. section 1.5
Use the architecture diagram to trace how the frontend, backend, and database divide responsibilities. section 1.4
