Orqestra · Request architecture
From interface to database
Authentication, business rules, and persistence in one Spring Boot application.
Angular Client
Initiates the request
Spring Security
Authentication & authorization
Controller / Service
Spring Boot business rules
Spring Data JPA
Repository persistence
PostgreSQL
Relational data storage
Follow one illustrative request through the verified application layers, then back to the client. No live data or API call is used.
What each layer does
Angular Client
The Angular interface initiates an API request. Frontend permissions help navigation; the server independently decides access.
Spring Security
The JWT authentication filter establishes identity. Endpoint and method-level checks enforce permissions; data access remains scoped to the authenticated user.
Controller / Service
Controllers expose HTTP endpoints. Services apply business rules and define transaction boundaries where needed.
Spring Data JPA
Spring Data repositories and Hibernate translate persistence operations. Queries, transaction boundaries and explicit locking support the workflow.
PostgreSQL
PostgreSQL stores business records. The application receives results through the repository and service layers, then returns an HTTP response to the client.
A conceptual trace of the repository’s current layers. Specific endpoints can take different paths. Inspect the source