System architecture
Service map
| Repository | Responsibility |
|---|---|
tuition-frontend | Angular 19, Material/Fuse layouts, reactive forms, searchable dropdowns, ledger and chart screens |
tuition-backend | Spring Boot 3.4 / Java 21, JPA/JDBC queries, business rules, Spring Batch, Flyway |
tuition-print | Laravel 13 / PHP 8.3+, DOCX rendering, PDF conversion, FTP templates, delivery checkpoints |
tuition-filer | Original NestJS implementation, retained as legacy context |
tuition-docs | Docusaurus documentation; static files served through Nginx |
Business database
Parents and students link to saved invoices. Invoice items carry the billed description and amount. The payment ledger adds TRX_INVOICE_PAYMENT, while the delivery outbox uses TRX_INVOICE_DELIVERY.
Payment and delivery are independent concepts. A parent can have an unpaid invoice that was delivered successfully, or a paid invoice whose notification failed.
Backend modules
common-313: entities and request/response models.repository-313: JPA repositories and aggregate JDBC queries.mapper-313: entity/model mapping.service-313: business operations, transaction boundaries, delivery dispatch.exception-313: shared exception responses.web-313: controllers, application configuration, batch configuration, migrations.
Frontend conventions
Pages are standalone Angular components. Form construction belongs in helper classes under forms/; API work lives in services. Existing screens use the shared FlexiTable where its CRUD shape fits.
mat-select-search normally returns selected objects. Its optional valueKey mode returns IDs or enum values for ledger filters and payment methods. Existing object-based forms keep their original behaviour.
Dashboard/Transaksi retain the chart-and-card layouts. The ledger is the dedicated detailed table.
Hosting boundaries
Frontend and backend deployment branches use the shared GitLab Docker template and Cloud Run. The print service uses cPanel with an account-local PHP runtime, private release folders, shared persistent state, and public entry files.
The deployment guide explains why their Docker/public-directory layouts differ.