How akej24/bookstore works
Project type and purpose
• This is a full-stack Bookstore application comprised of:
• A React.js frontend (hosted separately at the frontend repo).
• A Java Spring Boot backend organized in three modules (monolith, domain, adapters, application).
• Supporting infrastructure (H2/relational database, Redis cache, RabbitMQ message broker).
• Users can register, log in, browse books, manage a shopping cart, checkout, place orders, and view order summaries. Administrators can manage deliveries and users.
File structure
• Top-level “bookstore” folder: multi-module Maven project.
• bookstore/domain: pure domain model (entities, value objects, exceptions).
• bookstore/application: application-service layer (handlers, repositories interfaces, event publishers/listeners).
• bookstore/adapters: adapter layer with Spring Boot Controllers, JPA repositories, JSON converters, security, RabbitMQ/Redis configs, caching, mail sender.
• bookstore/monolith: a standalone monolith version (for reference/tests).
• Infrastructure config files in adapters/src/main/resources: Liquibase changelogs, SQL scripts, Redis and RabbitMQ configs, application-*.yml.
• docker-compose.yml and Dockerfile: orchestrate containers for backend, Redis, RabbitMQ, and database.
README for additional insights
• Confirms monolithic Spring Boot architecture separated into layers.
• Lists core technologies: Spring Security (JWT), JPA/Hibernate, Redis cache, RabbitMQ messaging, Liquibase migrations, Ehcache, Spring Mail.
• Provides run instructions: Docker Compose brings up all services.