shanmukht9/quickserve-fe

Purpose and Entry Points

QuickServe is a Spring Boot backend for a service-ordering workflow: user authentication, catalog/homepage and menu discovery, cart validation, order placement/partner acceptance, and payment processing. Application bootstrap: src/main/java/com/quickserve/QuickServeApplication.java. HTTP entry points are controllers under src/main/java/com/quickserve/presentation/, notably OrderController.java, PaymentController.java, and AuthController.java.

Layered / Ports-and-Adapters Design

The core is structured as presentation → application use cases → domain ports → infrastructure adapters. Domain entities and persistence-independent interfaces define the business boundary in src/main/java/com/quickserve/domain/entity/Order.java, src/main/java/com/quickserve/domain/port/OrderRepositoryPort.java, and src/main/java/com/quickserve/domain/port/CatalogRepositoryPort.java. Implementations bind those ports to JPA, Redis, Firebase, and payment systems.

Identity and Request Security

OTP-based onboarding/authentication and JWT refresh are application workflows: src/main/java/com/quickserve/application/usecase/RequestOtpUseCaseImpl.java, src/main/java/com/quickserve/application/usecase/VerifyOtpUseCaseImpl.java, and src/main/java/com/quickserve/application/usecase/RefreshTokenUseCaseImpl.java. Requests traverse JWT security filtering and security configuration before protected controllers: src/main/java/com/quickserve/infrastructure/security/JwtAuthenticationFilter.java and src/main/java/com/quickserve/infrastructure/security/SecurityConfig.java.

Catalog, Homepage, and Cache

Homepage and menu use cases assemble banners, sections, category trees, and offerings through catalog ports: src/main/java/com/quickserve/application/usecase/GetHomepageUseCaseImpl.java, src/main/java/com/quickserve/application/usecase/GetMenuUseCaseImpl.java, and src/main/java/com/quickserve/domain/entity/HomepageSkeleton.java. Redis-backed homepage/offering caches provide a read-performance boundary in src/main/java/com/quickserve/infrastructure/cache/RedisHomepageCacheAdapter.java and src/main/java/com/quickserve/infrastructure/cache/RedisOfferingCacheAdapter.java. Domain update events drive invalidation/rebuild behavior via src/main/java/com/quickserve/infrastructure/invalidation/CacheInvalidationListener.java and src/main/java/com/quickserve/infrastructure/async/OfferingRebuildService.java.

Order and Partner Dispatch Flow

Cart validation precedes placement, producing validated items and summaries before an order is persisted: src/main/java/com/quickserve/application/usecase/ValidateCartUseCaseImpl.java, src/main/java/com/quickserve/application/usecase/PlaceOrderUseCaseImpl.java, and src/main/java/com/quickserve/domain/entity/CartSummary.java. Partner selection and acceptance are separate state transitions represented by src/main/java/com/quickserve/application/usecase/SelectPartnerUseCaseImpl.java, src/main/java/com/quickserve/application/usecase/OrderAcceptUseCaseImpl.java, and src/main/java/com/quickserve/domain/entity/PartnerDispatchEvent.java. Firebase is the outbound dispatch/notification integration boundary through src/main/java/com/quickserve/domain/port/FirebaseDispatchPort.java and src/main/java/com/quickserve/infrastructure/persistence/adapter/FirebaseAdapter.java.

Payments and Webhooks

Payment-option retrieval, order/payment handling, and Razorpay webhook processing are isolated use cases: src/main/java/com/quickserve/application/usecase/GetPaymentOptionsUseCaseImpl.java, src/main/java/com/quickserve/application/usecase/HandleRazorpayWebhookUseCaseImpl.java, and src/main/java/com/quickserve/infrastructure/payment/RazorpayService.java. External Razorpay callbacks enter through src/main/java/com/quickserve/presentation/PaymentWebhookController.java; resulting payment state is persisted through src/main/java/com/quickserve/domain/port/PaymentRepositoryPort.java.

Persistence, Runtime, and Operations

The service uses Spring Boot/JPA with database schema migration at src/main/resources/db/migration.sql; repository adapters map domain models to JPA entities, including src/main/java/com/quickserve/infrastructure/persistence/adapter/OrderPersistenceAdapter.java and src/main/java/com/quickserve/infrastructure/persistence/entity/OrderJpaEntity.java. Material infrastructure includes Redis, Firebase, Razorpay, AWS SQS configuration, async execution, and scheduled processing: src/main/java/com/quickserve/config/RedisConfig.java, src/main/java/com/quickserve/config/FirebaseConfig.java, src/main/java/com/quickserve/config/AwsSqsConfig.java, and src/main/java/com/quickserve/infrastructure/batch/NightlyRatingBatchJob.java. Local container dependencies are indicated by docker-compose.yml.