How uckgiduckgi/payall-be works
Project type and purpose
• This is a Java Spring Boot backend service (“PayAll_BE”) that implements a monolithic, layered architecture.
• It exposes a REST API for customers to manage accounts, carts, payments, products, purchases, receipts, recommendations, searches, statistics, stores, and users.
• It also provides global concerns: authentication/authorization (JWT + Redis), external integrations (crawling product API, MyData API), configuration (Redis, RestTemplate, Swagger), health-monitoring, and exception handling.
File structure
• Top-level: build scripts (Gradle), CI/CD workflows, settings, and a README (minimal content).
• src/main/java/com/example/PayAll_BE:
• customer/* – contains subpackages for each business domain, each following the pattern:
– Entity class
– Repository (Spring Data JPA)
– Service (business logic)
– Controller (REST endpoints)
– DTOs and Mappers for input/output
• global/* – cross-cutting modules:
– api (standard ApiResult wrapper)
– auth (controllers, services for login/register/refresh, JwtService, RedisService)
– config (RedisConfig, RestTemplateConfig, SwaggerConfig, security setup, monitoring beans)
– crawlingProduct (HTTP client for external product data)
– exception (custom exceptions and global handler)
– mydata (controllers and services for integrating with external MyData API)
• src/main/resources: simple resource file (temp.txt)
• src/test/java: unit tests for each controller and integration points
README
• The README contains only a placeholder link to the project owner’s GitHub.