manoharsamvel24/digital-store

Purpose and Runtime

This is a server-rendered digital-product store. A Java Spring Boot application runs Spring MVC, Spring Data JPA/Hibernate, Thymeleaf templates, and embedded Tomcat; MySQL is the persistence service. Products represent downloadable eBooks, music, photography, and software.

Entry point: src/main/java/com/app/digital_store/DigitalStoreApplication.java. Runtime configuration is in src/main/resources/application.properties.

HTTP Presentation Layer

Controllers own browser/API request routing and select the user/admin views:

• src/main/java/com/app/digital_store/controller/LoginController.java

• src/main/java/com/app/digital_store/controller/ApiController.java

Thymeleaf pages form the primary UI boundary, including registration/login, catalog/welcome, purchase, download, and admin flows:

• src/main/resources/templates/login.html

• src/main/resources/templates/buyProduct.html

• src/main/resources/templates/admin.html

ApiController is the REST-oriented boundary for clients such as Postman, while the login controller supports the server-rendered journey.

Identity, Sessions, and Admin Boundary

Users register and authenticate through the controller/service/repository stack. The domain user model carries the persisted account and download-related state:

• src/main/java/com/app/digital_store/entity/User.java

• src/main/java/com/app/digital_store/service/UserService.java

• src/main/java/com/app/digital_store/repository/UserRepository.java

Admin authentication/session state is separately handled by src/main/java/com/app/digital_store/config/AdminSessionManager.java. This establishes a privileged boundary around administration rather than exposing dashboard operations publicly.

Product Catalog and Management

Products are typed domain records, accessed through a service boundary over JPA repositories:

• src/main/java/com/app/digital_store/entity/Product.java

• src/main/java/com/app/digital_store/entity/ProductType.java

• src/main/java/com/app/digital_store/service/ProductService.java

• src/main/java/com/app/digital_store/repository/ProductRepository.java

The expected flow is catalog/category browsing → product selection → purchase/download page. Admin operations add, delete, search, and inspect catalog/user records through the same persistence-backed domain.

Purchase and Download Flow

A user selects one product per transaction, submits simulated payment credentials, reaches a success state, and receives the corresponding asset. Successful transactions update the user’s download count in MySQL. Key UI stages are:

• src/main/resources/templates/buyProduct.html

• src/main/resources/templates/paymentSuccess.html

• src/main/resources/templates/downloadPage.html

Payment is application-local simulation using account number and PIN; no external payment gateway is identified.

Static Asset Delivery and Bootstrap Data

Downloadable files are packaged as static Spring resources and served directly by the application:

• src/main/resources/static/downloads/ebook

• src/main/resources/static/downloads/music

• src/main/resources/static/downloads/software

src/main/java/com/app/digital_store/config/ProductSeeder.java initializes product/catalog data, coupling persisted product metadata to these packaged download assets. This makes deployment artifact contents part of the product-delivery boundary.