How ziruiwang1996/textbook-exchange-platform works
Project type and purpose
• This is a web-based textbook exchange platform built on a microservices architecture.
• It provides user authentication, cart management, order processing, and payment handling, communicating via RabbitMQ events.
File structure
• Top-level Spring Boot application (BookstoreApplication.java) under src/main/java/com/cse687/zirui/bookstore
• Four logical “service” folders:
• auth/ (authentication)
• cart/ (cart management)
• order/ (order processing & inventory)
• payment/ (payment processing)
• Each service folder follows the same substructure:
• controller/ (REST endpoints)
• domain/ (commands, events, models)
• messaging/ (RabbitMQ producers, consumers, config)
• repository/ (JPA repositories)
• service/ (business logic)
• Shared resources: Thymeleaf templates (src/main/resources/templates), application.properties, Docker Compose, pom.xml
README for additional insights
• Confirms microservices: auth, cart, order, payment
• Event-driven communication via RabbitMQ routing keys (e.g., auth.evt.loggedIn, cart.evt.orderPlaced, payment.evt.succeeded)
• Uses Java 21 + Spring Boot, MySQL, JPA/Hibernate, RabbitMQ, Thymeleaf
Detail
• Break each service into sub-components if space allows (Controller, Service, Repository, Messaging)
• JWT token generation in Auth Service and usage header in downstream calls
• Don’t over-simplify—capture all four services, the message broker, the database, and the UI in one cohesive view