How hyeonsangjeon/vertx-embedded-springboot works
Key Components to Include:
Client Layer
• External clients making HTTP requests
• Port 8989 for Vert.x communication
Vert.x Layer
• Worker Verticles (VertxWorker.java) with a note showing 4 worker instances
• Event Loop with 6 instances
• SpringVerticleFactory for Vert.x-Spring integration
Spring Boot Layer
• Main Application component
• Spring Boot embedded server (port 9000)
• Actuator component (port 7979)
MVC Architecture Components
• Controllers/Handlers (RequestHandler, RouteHandler)
• Services (BookAsyncService, BookServiceImpl)
• Repositories (BookRepository)
• DAOs (BookDao)
• DTOs (Book)
Database Layer
• Both H2 and MariaDB options
• Liquibase migration component
• MyBatis integration
• [Client Layer]
• ↓
• [Vert.x Layer]
• ↓
• [Spring Boot Layer]
• ↓
• [MVC Components]
• ↓
• [Database Layer]
Connection Types
• Double lines: Data flow
Special Notations
• Async worker threads (4 instances)
• Event loop threads (6 instances)
• Port numbers (8989, 9000, 7979)
• Liquibase migration flow
Key Interactions to Highlight:
Request Flow
• Client → Vert.x Facade (8989) → Worker Verticles → Spring Services → Database
Database Migration Flow
• Liquibase → Database (on deployment)
Monitoring Flow
• External Monitor → Actuator (7979) → System Status
Additional Elements:
Configuration components
• DataSourceConfig
• Application properties
• Logging configurations
Keep the following aspects in mind:
• Asynchronous nature of the system
• Clear separation between Vert.x and Spring Boot components
• Scalability aspects (worker threads, event loops)
• Database migration and monitoring capabilities