2. Final Report Tasniflagich

3.1.1 Laravel architect
Laravel implements MVC architecture. MVC is a software architecture that separates
domain/application/business logic from the rest of the user interface. It does this by separating
the application into three parts: the model, the view, and the controller. The following Figure 3
describes laravel workflow:
1. User via client application sends request to Backend’s API
2. Route send data to Controller to perform Business logic
3. Controller interact with Model
a. Model creates query to Database
b. Model get data from Database
4. Backend responses to request with existing data
5. Client software reacts to response and changes DOM.
Figure 3. Laravel workflow
3.2 About Composer
All starts from Composer. Composer is a tool for dependency management in PHP. It
allows you to declare the libraries your project depends on and it will manage (install/update)
them for you. In order to create a Laravel project we have to install composer package first. It
will load all necessary dependencies and libraries to a dedicated project.
The project folder in initialisation of Laravel via Composer contains folders:
TTPU
13
2022

---

1. app - The app directory contains the core code of the application
2. bootstrap - The bootstrap directory contains the app.php file which bootstraps the
framework. This directory also houses a cache directory which contains
framework generated files for performance optimization such as the route and
services cache files
3. config - the config directory, as the name implies, contains all of the application's
configuration files
4. database - The database directory contains database migrations, model factories,
and seeds
5. lang - The lang directory houses all of application's language files
6. public - The public directory contains the index.php file, which is the entry point
for all requests entering application and configures autoloading
7. resources - The resources directory contains views as well as raw, un-compiled
assets such as CSS or JavaScript
8. routes - The routes directory contains all of the route definitions for the
application.
9. storage - The storage directory contains logs, compiled Blade templates, file
based sessions, file caches, and other files generated by the framework
10. tests - The tests directory contains automated tests
11. vendor - The vendor directory contains Composer dependencies