How dplearncs/e-commerce-application works
Project type and purpose
• This is a console-based, monolithic E-commerce application written in Java.
• It simulates basic user and product management with file-based persistence and input validation, following OOP principles.
File structure
• Top-level “src” folder contains 5 packages:
• inputValidator (InputValidator.java, ReturnValues.java)
• main (Main.java)
• models (User, Admin, Customer, Product)
• services (ECommerceApp.java, UserService.java, ProductService.java)
• storage (FileService.java)
• No external web or database services—persistence is via Java I/O to flat files.
• The entry point is Main.java, which drives console I/O.
README
• Confirms core features: user auth, product CRUD, order placement, order history.
• Emphasizes file-based storage and input validation.
a. Main components
• Presentation Layer – Main.java (console UI)
• Input Validation – InputValidator, ReturnValues
• Service Layer – ECommerceApp orchestrator, UserService, ProductService
• Data Model – domain objects in models package
• Persistence Layer – FileService (file I/O)
b. Relationships & interactions
1. Main → ECommerceApp.run() to start the app loop
2. Main reads user commands, delegates to InputValidator
3. Validated input → ECommerceApp routes to UserService or ProductService
4. Services ←→ models (create, update domain objects)
5. Services → FileService for save/load operations
6. FileService reads/writes domain data to disk
c. Architectural patterns & principles
• Layered architecture (Presentation → Validation → Services → Persistence)
• Single Responsibility per package/class
• Dependency direction: higher layers depend on lower ones, not vice versa
d. Key technologies
• Java core libraries
• java.io for FileService
• OOP classes for models and services