How shady1997/-mobile_bank_api_restful works
Project type and purpose
• This is a standalone Spring Boot 3.2.0 RESTful API service (“Mobile Banking REST API”) implemented in Java 17.
• Purpose: Provide core mobile banking operations (user, account, transaction management) via HTTP endpoints, with H2 in-memory DB for persistence, Swagger/OpenAPI docs, basic auth security, and comprehensive testing.
File structure
• Top level:
• dockerfile, pom.xml, README.md, LICENSE, .github (CI/CD deploy.yml)
• src/main/java/org/banking:
– config (SecurityConfig, OpenApiConfig)
– controller (AccountController, TransactionController, UserController)
– service (AccountService, TransactionService, UserService)
– repository (Spring Data JPA interfaces)
– model (JPA entities)
– dto (API data transfer objects)
– exception (custom exceptions, global handler)
– entrypoint: MobileBankingApiApplication.java
• src/main/resources/application.yml (datasource, H2, Hikari)
• src/test: unit & integration tests
• Pattern: classic layered MVC (Controller → Service → Repository → Database), plus cross-cutting concerns (security, validation, global exception handling).
README for additional insights
• Confirms tech stack (Spring Boot, Java, H2, JPA/Hibernate, Spring Security, OpenAPI, RestAssured).
• Lists features (CRUD, transactions, validations, error handling, Swagger UI, H2 console).
• Outlines DB schema (users, accounts, transactions tables).
• Mentions deployment (Dockerfile), CI/CD workflow, and production security recommendations.
Final recommendations
• Every package as a component: config, controller, service, repository, model, dto, exception.
• Infrastructure (Docker, CI/CD) and non-functional elements (security, validation, testing) as side modules.
• Use this detailed layered view to communicate the complete architecture to stakeholders and new team members.