How assem-gh/el-shop works
Project type and purpose
• Frontend: a React+TypeScript single-page app built with Vite, using Redux slices, Axios API calls, and a component hierarchy.
• Backend: a Spring Boot (Java/Maven) REST API with Controllers, Services, Repositories, integration with AWS S3 and Keycloak for auth, packaged and containerized via Docker.
File structure
• Top-level directories:
• frontend/ – React app (vite.config, tsconfig, package.json, src/components, src/pages, src/store, etc.)
• backend/ – Spring Boot service (pom.xml, src/main/java/com/elshop/backend/{category,product,common,config,exception}, resources, tests)
• . github/workflows/ – CI pipelines (analyse, deploy)
• Patterns:
• Backend follows MVC: Controller → Service → Repository (Spring Data JPA).
• frontend follows feature-based module organization (components, pages, store slices).
• Infrastructure/deployment:
• backend/Dockerfile, Maven wrapper
• GitHub Actions YAMLs for CI/CD
• sonar-project.properties for code quality
README
• README is minimal, so all insights come from directory names and file naming conventions.
Essential architectural elements
• Every major folder or module as a discrete component.
• How frontend state management (Redux slices) maps to backend entities (Product, Category).
• Authentication/authorization flow via Keycloak.