How rocha7778/reactive-movie-reviews-service works
Project type and purpose
• From the file tree and README, we see a single Spring Boot application called “reactive-movie-reviews-service.”
• It’s a reactive, back-end service (no “frontend” folder) exposing a REST API for CRUD operations on movie reviews.
• It uses Spring WebFlux (functional router+handler) and a reactive data repository (Spring Data Reactive).
File structure
• Top-level: pom.xml, mvnw scripts, .mvn wrapper → a Maven-built Java Spring Boot project.
• src/main/java/com/rocha/aws/app:
• ReactiveMovieReviewsServiceApplication.java – the Spring Boot entry point.
• domain/Review.java – the domain model for reviews.
• route/ReviewRouter.java – functional routing definitions (endpoints).
• handler/ReviewHandler.java – the business logic for each route.
• repository/ReviewReactiveRepository.java – reactive CRUD against the data store.
• error/handler/* – a chain of ExceptionHandler implementations for custom error responses.
• src/main/resources/application.properties – externalized configuration.
• Tests in src/test/java mirror the main code’s structure.
README for additional insights
• The README only contains the project name, so we infer architecture purely from code structure.
Capturing essential details
• Folder’s responsibility as a separate component.
• Exception handling strategy as its own micro-component.
• Don’t overload: keep the focus on request → reactive processing → DB → response.