How mans14team/library_management works
Project type and purpose
• LibMate is a monolithic, full-stack Java/Spring Boot web service for library management: book/catalog metadata, physical book copies, rental/return/reservation, study-room reservations, membership payments, reviews, bulletin board, real-time notifications, full-text search, and centralized logging.
File structure
• Top‐level: Dockerfile, docker-compose.yml, .ebextensions (Elastic Beanstalk), nginx/, .github/workflows (CI/CD), gradle wrappers.
• src/main/java/com/example/library_management: domain modules (auth, book, bookCopy, bookRental, bookReservation, board, room, reviews, membership, notifications, data ingestion, common utilities), global configs (Spring, JPA, Redis, RabbitMQ, Elasticsearch, security, OAuth2), scheduling, exception handling.
• src/main/resources: application.yml for dev/prod profiles.
• docker/: stack for elasticsearch, filebeat, logstash (ELK).
• backup/: CSV data for room reservations.
• Tests follow the same package structure.
README for additional insights
• Key features: concurrency control (optimistic lock + Redis distributed lock), real-time notifications (RabbitMQ), caching (Redis), full-text search (Elasticsearch), centralized logging (ELK), CI/CD (GitHub Actions → AWS Elastic Beanstalk), Dockerization, AWS services (RDS, ElastiCache, ECR).
• Infrastructure sketch shows Client → NGINX → Dockerized Spring Boot on EB → MySQL, Redis, Elasticsearch, RabbitMQ; Filebeat/Logstash → Elasticsearch for logs; GitHub Actions pipeline.