How avinash026/spring-webflux-reactive-databases works
Main Components
• product-api: A Spring Boot WebFlux application that manages products and uses MongoDB as its data store.
• customer-api: A Spring Boot WebFlux application that manages customers with Postgres as its storage.
• order-api: A Spring Boot WebFlux application that manages orders, stores data in Cassandra, and uses non-blocking WebClient (and CompletableFuture) to retrieve extra details (like customer details and product info) from customer-api and product-api.
• notification-api: A Spring Boot WebFlux application that manages notifications, which uses MySQL for persistence and also may depend on other APIs (e.g., customer-api and order-api) to obtain necessary information.
• client-shell: A Spring Boot Shell application that provides commands to interact with the various REST APIs offered by the above services.
Data Stores
• MongoDB for product-api
• Postgres for customer-api
• Cassandra for order-api
• MySQL for notification-api
Relationships and Interactions
• The client-shell acts as an entry point for users, sending commands that trigger REST API calls to product-, customer-, order-, and notification-api.
• Each API connects directly with its underlying database.
Architectural Patterns & Design Principles
• Reactive/non-blocking design pattern since Spring WebFlux is used across the board.
Final Reminders
• Use clear, self-explanatory labels for each module.