How diegomouraoficial/sistema-bancario works
Project type and purpose
• This is a Java-based RESTful web application (full-stack backend) built with Spring Boot.
• Purpose: provide a banking system API to manage customers (“Cliente”) and accounts (“Conta”), execute transactions and transfers, backed by a PostgreSQL database.
File structure
• Top-level: pom.xml, Maven wrapper, README → Maven-based build.
• src/main/java/br/com/diego/olabi:
• BlackApplication.java — entry point (SpringBootApplication)
• controller/…Controller.java — REST controllers for “clientes” and “contas”
• service/…Service.java — business logic layer
• repository/…Repository.java — Spring Data JPA interfaces → database access
• model/… — JPA entity definitions (Cliente, Conta)
• dto/… — data transfer objects for API responses
• request/… — request payload objects
• exception/… — custom exceptions (InsufficientFunds, ResourceNotFound)
• enums/… — domain enums (TipoConta)
• src/main/resources/application.properties — DB configuration
• src/test — basic integration/unit test of application context.
README
• Tech stack: Java 11+, Spring Boot, Spring Data JPA, PostgreSQL.
• Describes DB setup, API endpoints, JSON schemas.
1. An actor (HTTP Client) on the left.
• Top: Controller Layer
• Middle: Service Layer
• Bottom: Repository Layer
3. Inside each section, list relevant packages/classes.
• Client → Controllers (POST /clientes/cadastrar, GET /contas/{id}, etc.)
• Controllers → Services
• Services → Repositories
• Repositories → Database
• Database → Services (on query result) → Controllers → Client
7. Notes on exception flows (e.g., ResourceNotFound → 404, InsufficientFunds → 400).