How navinreddy20/ecom-proj works
This is a Spring Boot product-catalog API. Clients create, retrieve, update, delete, and search products; image uploads are stored with product records and image data can be retrieved separately. The controller delegates operations to a service, which uses a JPA repository over the Product entity. Source excerpts establish those calls and the persistence abstraction; database configuration and startup wiring are not shown, so the startup-to-controller link is unverified.
Main entry points: ProductRepo.java Product repository · ProductController.java Product controller · ProductService.java Product service · EcomProjApplication.java Spring Boot app
Components 7
API
- Product controller
src/main/java/com/telusko/ecom_proj/controller/ProductController.java
Catalog domain
- Product service
src/main/java/com/telusko/ecom_proj/service/ProductService.java - Product entity
src/main/java/com/telusko/ecom_proj/model/Product.java
Persistence
- Product repository
src/main/java/com/telusko/ecom_proj/repo/ProductRepo.java - JPA database
Runtime
- Spring Boot app
src/main/java/com/telusko/ecom_proj/EcomProjApplication.java
Other components
- API client
Connections 6
- API client → Product controller: sends requests
src/main/java/com/telusko/ecom_proj/controller/ProductController.java - Product controller → Product service: delegates operations
src/main/java/com/telusko/ecom_proj/controller/ProductController.java - Product service → Product repository: calls queries
src/main/java/com/telusko/ecom_proj/service/ProductService.java - Product repository → Product entity: maps records
src/main/java/com/telusko/ecom_proj/repo/ProductRepo.java - Product repository → JPA database: persists via JPA
src/main/java/com/telusko/ecom_proj/repo/ProductRepo.java - Spring Boot app → Product controller: starts web app