How q4erty/ent-dev-mid works
Project type and purpose
• This is a full-stack, microservices-based task management application.
• It consists of two independent Spring Boot services (“orm-api” and “sql-api”) for REST APIs, plus a React+Vite SPA as the user interface.
• It uses PostgreSQL and MySQL for data persistence and is designed to scale horizontally.
File structure
• Top level:
• backend/orm-api (Gradle-built Spring Boot service with JPA entities, controllers, repositories)
• backend/sql-api (Maven-built Spring Boot service with JDBC/SQL-first style)
• frontend/ (React+Vite single-page app: pages, services/api.jsx, Vite config)
• Both backend folders follow the standard Spring Boot src/main/java and src/main/resources layout.
• No API gateway or message broker—clients call each service directly.
Key insights from README
• Microservices architecture: “modular architecture (frontend + backend separation).”
• Tech stack badges confirm Java 21, Spring Boot 3.3, React 18, Vite 5, PostgreSQL 16, MySQL 8.0.
• Build: Maven for sql-api, Gradle for orm-api.
• Run instructions show each service listening on its own port and the SPA on port 5173.