JeecgBoot is an enterprise-grade low-code development platform that accelerates application delivery through AI-powered code generation, online form/report builders, and workflow integration. The backend is built on Spring Boot 3 with MyBatis-Plus, Shiro, and JWT, supporting both monolithic and microservice architectures (Spring Cloud, Nacos, Sentinel, XXL-Job). The frontend uses Vue 3 + TypeScript + Ant Design Vue with a rich component library including JVxeTable for editable grids and schema-driven forms. The platform provides comprehensive RBAC, multi-tenancy, dynamic data sources, data dictionaries, and third-party integrations (DingTalk, WeChat, Feishu). A dedicated AI module (airag) offers RAG knowledge bases, LLM chat, voice/image generation, and MCP plugin support. The codebase is actively maintained with frequent commits and a large community, though it contains some commented-out legacy code and hardcoded security values that represent minor technical debt.
ruoyi-vue-pro (芋道) is a large-scale, multi-module enterprise rapid development platform built on Spring Boot 2.7, MyBatis-Plus, and Vue 3. It provides a comprehensive backend infrastructure for building business applications such as ERP, CRM, HRM, MES, WMS, OA, BPM (Flowable), IoT, AI, IM, Pay, Mall, and more. The codebase is structured around a reusable framework layer (`yudao-framework`) with many Spring Boot starters for security, data permission, multi-tenancy, WebSocket, Excel, monitoring, and protection (rate limiting, idempotency). Business modules follow a consistent layered pattern (DO → Mapper → Service → Controller → VO) with MapStruct converters. The system supports MySQL, PostgreSQL, Oracle, SQL Server, and Dameng databases, and integrates with Redis, RabbitMQ, Kafka, RocketMQ for messaging. It includes a code generator, a workflow designer, and AI chat/image/mind-map capabilities. The architecture is modular and well-organized, though the sheer number of modules (20+) introduces some duplication and complexity. Overall, it is a mature, actively maintained project with strong adherence to common enterprise patterns.
DynamicTp is a Java library for dynamic thread pool management, primarily targeting Spring Boot applications. It allows runtime modification of thread pool parameters (core size, max size, queue capacity, etc.) via configuration centers like Nacos, Apollo, Zookeeper, Consul, Etcd, and Polaris. The library provides a rich set of executor variants (eager, ordered, priority, scheduled) and integrates with over a dozen middleware frameworks (Dubbo, gRPC, RocketMQ, RabbitMQ, Tomcat, Jetty, Undertow, Hystrix, Motan, OkHttp3, Thrift, SofaRPC, Tars, LiteFlow, brpc) by wrapping their native thread pools. It includes comprehensive monitoring and alerting: metrics collection via Micrometer, JMX, and logging; notification channels for DingTalk, WeChat, Lark, email, and custom notifiers; and alarm thresholds for capacity, liveness, rejections, and timeouts. The architecture is modular: a core module defines executors, registries, and lifecycle management; a common module provides utilities, parsers, queues, and SPI extension points; adapter modules wrap middleware executors; starter modules provide Spring Boot auto-configuration; and extension modules add optional features like Redis rate limiting and OpenTelemetry tracing. Key entry points are the @EnableDynamicTp annotation, DtpRegistry for executor registration, and ThreadPoolBuilder for programmatic pool creation. External dependencies include Spring Boot, Guava EventBus, ByteBuddy (for interception), Micrometer, and various config-center client libraries.
RuoYi is a production‑ready Java rapid‑development framework for building enterprise back‑office management systems (CMS, CRM, OA, etc.). It is a monolithic Spring Boot application using Apache Shiro for authentication/authorization, MyBatis for persistence, Thymeleaf for server‑side rendering, and a jQuery/Bootstrap frontend with numerous third‑party plugins. The system provides a complete RBAC module (user, role, department, menu management), dictionary and configuration management, operation and login auditing, online user monitoring, Quartz‑based scheduled tasks, and a Velocity‑powered code generator that produces full CRUD modules from database tables. Additional features include dynamic data source switching, XSS/CSRF protection, captcha, file upload/download, Excel import/export with annotation‑driven mapping, and a demo suite for UI components. The architecture follows a modular Maven structure (admin, common, framework, system, generator, quartz) with a shared common module providing utilities, annotations, and exception hierarchy. While the framework is mature and widely adopted, its frontend stack (jQuery, Bootstrap 3‑era plugins) and use of Shiro represent technical drift compared to modern SPA or Spring Security approaches. The codebase is well‑organized and contains several reusable components, but is tightly coupled to its own conventions and lacks microservice readiness.
This is a comprehensive e-commerce backend platform built with Spring Boot 3.5+, JDK 17, and a multi-module Maven architecture. In production, it serves two distinct APIs: `mall-admin` (admin management) and `mall-portal` (customer-facing storefront), plus a dedicated `mall-search` module for Elasticsearch-powered product search. The system handles product cataloging, order lifecycle management, user registration/authentication, coupon and promotion calculations, shopping cart operations, payment integration (Alipay), and content management (home page banners, recommendations). It uses MySQL as the primary database via MyBatis (with generated mappers), Redis for caching and session management, MongoDB for user activity data (browsing history, favorites), RabbitMQ for delayed order cancellation, and MinIO/Aliyun OSS for file storage. Security is implemented with Spring Security and JWT, including dynamic path-based authorization. The codebase follows a layered architecture (Controller → Service → Mapper/DAO) with shared modules `mall-common` and `mall-security` providing reusable utilities for API responses, pagination, exception handling, Redis caching, and authentication. While heavily reliant on MyBatis Generator for data access objects and includes some long service methods, the overall structure is well-organized and modular, making it suitable as a reference for similar e-commerce projects. No data research or analytical components are present; this is purely an application codebase.
The repository is a full-stack application template providing role-based access control (RBAC) with a modern frontend and multiple backend options. It features a React/Vite frontend built with Shadcn UI and Tailwind CSS, offering comprehensive UI components, dashboards, and charting capabilities. Two backend implementations are provided: Spring Boot (Java) and NestJS (TypeScript), both featuring JWT authentication, PostgreSQL integration, and CRUD operations for users, roles, permissions, and groups. The frontend showcases a well-crafted component library including reusable UI primitives, custom extensions like tree selectors and context menus, and themed chart containers. State management is handled via Zustand, with internationalization via react-intl and API mocking using MSW. The backends follow standard layered architectures with service-repository patterns, DTO validation, and security configurations. While the Spring Boot backend contains a non-standard Java 25 version specification (likely a typo) posing build risks, the NestJS backend uses current LTS Node.js versions. The project demonstrates solid full-stack engineering with modular design, clear separation of concerns, and reusable UI patterns. Despite the Java version concern in one backend, the template remains a valuable foundation for enterprise admin panels with modern tooling.
This repository provides a full-stack demonstration of a permission management system using Spring Boot for the backend and Vue.js for the frontend. Despite its name, it does not use Apache Shiro; instead, it implements a custom, annotation-based permission control via AOP (RequiresPermissions annotation and PermissionAspect) and token-based authentication using Caffeine local cache. The backend is a monolithic Spring Boot 2.3.10 application with MyBatis for database access, serving a REST API. The frontend is a Vue 2 application (based on vueAdmin-template) with dynamic routing and ElementUI, featuring a custom directive for button-level permission checks. The system supports multi-role users, role-based menu and permission assignment, and a clean separation of concerns between backend and frontend permission enforcement. The codebase is well-structured and serves as a clear reference for implementing RBAC-like permission systems in Java+Vue projects, though it is not intended for production use without significant hardening and updates.
This repository is the source code for an Elasticsearch tutorial e-book, built with VuePress to generate a static website. The content covers Elasticsearch 7.9.3, including installation, basic and advanced operations, architecture, and practical examples. The site is deployed via a simple shell script that builds the VuePress site and pushes to GitHub Pages. While the repository primarily serves as educational material, it also includes standard VuePress configuration and deployment scripts typical of documentation sites.
mini-spring-cloud is an educational, simplified reimplementation of core Spring Cloud components, designed to help developers understand the underlying principles of service registration, discovery, client-side load balancing, declarative HTTP clients (Feign), and API gateway (Zuul). The codebase implements a custom lightweight registry called 'Tutu' and integrates with Netflix Ribbon, OpenFeign, and Netflix Zuul libraries. It follows Spring Cloud Commons abstractions and uses Spring Boot auto-configuration. The project is not intended for production use; it serves as a learning resource with minimal error handling, incomplete feature coverage (e.g., only POST mapping support in Feign contract), and no comprehensive test suite. The architecture is modular with separate Maven modules for each concern, and the code is clean and well-commented in Chinese. However, dependencies are somewhat outdated (Spring Cloud 2021.0.1, Ribbon 2.3.0, Zuul 1.3.1) and the project has not seen recent updates.
This is a large, sprawling collection of tutorial and demo projects authored by a single developer (blogger '程序员欣宸'). It covers dozens of technologies including Spring Boot internals, Flink, Kafka, gRPC, JavaCV/OpenCV, Kubernetes controllers, LangChain4j, JUnit 5, and more. Each subdirectory is an independent, self-contained demo typically with a single main class or test. The code is educational: full of Chinese comments, simplified logic, and hardcoded paths. While not a cohesive application, it serves as a rich reference for learning how to use specific frameworks and patterns. The quality is average overall—functional but boilerplate-heavy, with many outdated dependencies and duplicated code across projects.
This repository is a meta-project for a Spring Cloud microservices demo, now superseded by the Opensabre framework. It contains no actual source code; instead, it aggregates several external submodules (opensabre-framework, base-authorization, base-organization, base-gateway, etc.) via Git submodules. The root pom.xml defines dependencies for Spring Boot 2.1.10, Spring Cloud Greenwich, and Alibaba Cloud 2.1.0, all of which are outdated. The README explicitly states that the project has been replaced by a newer version. As a standalone repository, it provides no reusable code or components; it serves only as a historical reference or a pointer to the submodules. The repository is effectively deprecated and should not be used for new projects.