devcyberlearnix-art/cyberlearnixapi

Purpose and topology

CyberLearnix is a Java/Spring LMS backend organized as independently deployable domain services. Gradle multi-project files (settings.gradle, build.gradle) coordinate modules; each service has a Spring Boot entry point and Dockerfile. The public edge is api-gateway/src/main/java/com/swachvega/apigateway/ApiGatewayApplication.java; local shared infrastructure is defined in docker/compose.yml and docker/init-databases.sql.

Edge gateway, identity, and authorization

The reactive API gateway routes requests, validates JWTs, and manages sessions backed by Redis. Its key request boundary is api-gateway/src/main/java/com/swachvega/apigateway/filter/JwtAuthenticationFilter.java, with session APIs in api-gateway/src/main/java/com/swachvega/apigateway/controller/SessionManagementController.java and Redis wiring in api-gateway/src/main/java/com/swachvega/apigateway/config/RedisConfig.java.

User service is the principal identity lifecycle owner: registration, unified login/refresh/password-reset/OTP flows, OAuth2 success handling, token blacklisting, sessions, audit logs, and instructor applications. Core paths: user-service/src/main/java/com/user/register/controller/UnifiedAuthenticationController.java, user-service/src/main/java/com/user/register/service/UnifiedAuthenticationService.java, and user-service/src/main/java/com/user/register/entity/UserSession.java. Services also contain local JWT filters/configurations; commonlibs/src/main/java/com/cyberlearnix/security/SharedJwtValidator.java provides a shared validation implementation.

Learning content and instructor operations

Course service owns learner-facing course structure and enrollment records: courses, sections, lectures, previews, and enrollments. Entry APIs are split across course-service/src/main/java/com/lms/courseservice/controller/CourseController.java, course-service/src/main/java/com/lms/courseservice/controller/EnrollmentController.java, and persistence entities under course-service/src/main/java/com/lms/courseservice/entity/.

Instructor service is a separate authoring and instructor-workflow boundary: instructor profiles, course/modules/content/resources, announcements/messages, dashboard and earnings data. It exposes authoring/public-course endpoints through instructor-service/src/main/java/com/example/instructorservice/controller/CourseController.java and instructor-service/src/main/java/com/example/instructorservice/controller/PublicCourseController.java; it integrates course data through instructor-service/src/main/java/com/example/instructorservice/integration/CourseIntegrationService.java. Cloudinary configuration indicates external media/document storage (instructor-service/src/main/java/com/example/instructorservice/config/CloudinaryConfig.java).

Discovery, cart, and promotions

Wishlist and cart are user-scoped commerce-preparation services. Both call course service through clients: wishlist-service/src/main/java/com/lms/wishlist_service/client/CourseClient.java and cart-service/src/main/java/com/lms/cart_service/client/CourseClient.java. Cart also calls coupons and handles checkout-oriented summaries in cart-service/src/main/java/com/lms/cart_service/service/CartServiceImpl.java.

Coupon service owns campaigns, coupons, usage/redeeming, validation, auto-apply, and referral/bulk operations. Its transactional boundary is represented by coupon-service/src/main/java/com/lms/coupon_service/entity/CouponUsage.java; service behavior is in coupon-service/src/main/java/com/lms/coupon_service/service/CouponServiceImpl.java. Redis is configured here (coupon-service/src/main/java/com/lms/coupon_service/config/RedisConfig.java).

Order, payment, and fulfillment flow

The commerce flow is synchronous service-to-service orchestration: order service reads cart and coupon state via Feign clients, persists orders/items/refunds, then payment service creates/verifies payment links/callbacks and handles refunds. Key integration points are order-service/src/main/java/com/lms/orderservice/client/CartClient.java, order-service/src/main/java/com/lms/orderservice/service/OrderService.java, and payment-service/src/main/java/com/lms/paymentservice/service/PaymentService.java.

Payment explicitly integrates PayU via payment-service/src/main/java/com/lms/paymentservice/service/PayUCommandService.java and payment-service/src/main/java/com/lms/paymentservice/service/PayUPaymentLinkService.java. It calls enrollment through payment-service/src/main/java/com/lms/paymentservice/client/EnrollmentClient.java, making successful payment the likely boundary that grants course access.

Engagement and moderation

Review service manages submitted reviews, ratings summaries, and administrative moderation. It verifies course/enrollment/user eligibility through Feign clients and fallbacks: review-service/src/main/java/com/lms/review/service/ReviewService.java, review-service/src/main/java/com/lms/review/client/EnrollmentClient.java, and review-service/src/main/java/com/lms/review/service/AdminReviewService.java.

Notification service persists notifications, delivery state, device tokens, templates, and user preferences; it supports course/instructor/admin/reminder workflows and sends push notifications through Firebase. Core paths: notification-service/src/main/java/com/example/notification/service/FirebasePushService.java, notification-service/src/main/java/com/example/notification/entity/DeviceToken.java, and notification-service/src/main/java/com/example/notification/service/NotificationService.java.

Administrative control plane

Admin service provides privileged authentication, bootstrap/main-admin setup, permission checks, audits, reports, and cross-service administration. It acts as an aggregation/orchestration layer through REST clients for users, courses, carts, coupons, instructors, notifications, and wishlists: admin-service/src/main/java/com/example/admin/controller/AdminController.java, admin-service/src/main/java/com/example/admin/service/AdminPermissionService.java, and admin-service/src/main/java/com/example/admin/client/AdminUserServiceClient.java. Its own persisted admin/course records and audit service establish a separate administrative authority boundary.