How nishiket-singh/bidwise-bidding-website works
Project type and purpose
• This is a full-stack web application named “BidWise.”
• Frontend: React single-page application (SPA) in the BidWiseClient folder.
• Backend: Spring Boot REST API in the group111 Maven project folder.
• Features: user signup/signin, product catalog, bidding engine, payment flow via Stripe, email notifications, auction-end processing.
File structure
• Top-level separation:
– BidWiseClient/ → React app: public assets, src components, pages, styles.
– group111/ → Spring Boot app: controllers, services, repositories, models, DTOs, exceptions, SQL scripts.
– Postman TestCases/ → collections for API endpoints (bidding, login, products, payments).
• Backend patterns:
– MVC / layered architecture:
· Controllers → REST endpoints
· Services → business logic (bidding, payment, authentication, email)
· Repositories → JPA data access
· DTOs ↔ domain models
– Configuration files: application.properties, data.sql, schema.sql
• Frontend patterns:
– Component hierarchy: pages under src/components/pages, shared components (navbar, footer, buttons).
– CSS modules for styling.
– HTTP calls from React to backend API.
Examining the README
• Tech stack called out: React, Spring Boot, SQL database, Stripe API.
• Deployment URLs illustrate public API and client hosting.
Main components
a. User’s Web Browser (React SPA)
b. React Application Layers
– UI Components → pages, buttons, forms
– API Service Layer (HTTP client)
c. Backend REST API (Spring Boot)
– Controllers (BiddingController, PaymentController, ProductController, UserController)
– Service Layer (BiddingService, PaymentService, AuthenticationService, EmailService, BiddingEndService)
– Repository Layer (JPA Repositories connected to SQL)
– Domain Models & DTOs
d. SQL Database (MySQL/PostgreSQL or in-memory H2)
e. External Services
– Stripe Payment API
– SMTP/Email Service (for notifications)
f. Postman Test Harness (optional external client)
Relationships and data flows
• User → React SPA: UI interactions (login, browsing, bidding, checkout).
• React SPA → Spring Boot API: REST calls (JSON over HTTP).
• API Controllers → Services → Repositories: internal request flow.
• Repository → SQL Database: CRUD operations on Users, Products, Bids, Orders, AuthTokens.
• PaymentService → Stripe API: payment authorization & capture.
• BiddingEndService (scheduled or event-driven) → triggers bid-closing logic, updates DB, sends email via EmailService.
Architectural patterns and design principles
• Layered architecture (presentation, service, data).
• Dependency Injection (Spring).
• DTO pattern to decouple API contract from persistence models.
• RESTful API design.
• Component-based UI (React).
• External integration points abstracted behind service interfaces (e.g., Stripe, Email).