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.
WePush is a Java application monorepo with two coexisting generations of a multi-channel bulk messaging system. The legacy `src/main` tree is a Swing desktop client that manages accounts, message templates, recipient lists, tasks, and run history, and sends via WeChat (official accounts, mini programs, WeCom), SMS vendors, email, HTTP, DingTalk/Feishu bots, and carrier SMS protocols (CMPP/SMGP/SGIP/SMPP). It persists to SQLite through MyBatis and generates UI with IntelliJ GUI Designer forms. The `next/` tree is a modular, distributed push orchestration platform: a Spring Boot control plane (REST + gRPC), remote agents connected via an mTLS gRPC stream, a provider SPI with built-in HTTP, Aliyun SMS, SMTP, WeChat, and bot providers, and pluggable signed PF4J plugins for carrier protocols. It adds multi-tenant workspaces, secret envelope encryption, artifact storage (local/S3), audience streaming import, run state machines with idempotency and retry, schedule management, a React/Vite web UI, an Electron desktop shell, and a Java SDK. Persistence is SQLite for standalone mode or PostgreSQL for server mode, with Flyway migrations and JDBC repositories. The Next codebase is well-architected with core-api/engine/provider-spi/service/domain/infrastructure separation, ADRs, architecture tests, integration tests, CI, and installers. However, the repository as a whole carries the legacy desktop codebase in parallel, duplicating several domain concepts and retaining generated UI code and older dependencies. This split and the aging legacy portions are the main sources of technical debt.
Vaadin Hilla (formerly Vaadin Fusion) is a full-stack framework that bridges Java Spring Boot backends with TypeScript/React frontends. Its core function is automatic, type-safe code generation: Java classes annotated with @Endpoint or @BrowserCallable are parsed into OpenAPI specifications, which are then used to generate TypeScript client stubs, form models (with validation constraints mapped from JSR-380 annotations), and reactive signal bindings. This eliminates the need for manual API contracts and provides end-to-end type safety between server and client. The framework also includes a file-based router, a CRUD layer (ListService, FormService) integrated with JPA repositories, and reactive full-stack signals for real-time data synchronization via WebSocket push. Architecturally, Hilla is a monorepo organized into Java backend packages (endpoint, engine-core, typescript-generator) and TypeScript frontend packages (generator-core, react-crud, react-form, file-router, react-signals). Build integration is provided through Maven and Gradle plugins that trigger code generation during the build lifecycle. The code generator follows a plugin-based pipeline where each plugin (backbone, model, signals, push, subtypes, transfertypes) processes the OpenAPI schema to produce specific TypeScript output. The frontend runtime includes a middleware-enhanced ConnectClient for HTTP calls, declarative authorization via @AnonymousAllowed/@RolesAllowed, and a full i18n system. Security is a first-class concern with CSRF protection, JWT support, and Spring Security integration demonstrated across multiple test applications. The system does not include data pipeline or research code; it is a production-ready application framework. Notable reusable artifacts include a clean validator pattern in lit-form, a generic CommandRunner interface for external process execution, tree-merging utilities in the file router, and the full-stack signal implementation that demonstrates a command-based reactive state pattern. The codebase is actively maintained with extensive integration tests, though some areas (snapshot tests, dual Lit/React support, Atmosphere push dependency) introduce maintenance complexity and potential drift risks.
rsql-jpa-specification is a library that translates RSQL (RESTful Search Query Language) queries into Spring Data JPA Specifications or QueryDSL Predicates. It supports complex queries including entity associations, JSONB fields (PostgreSQL), custom operators, property mapping, and sorting. The architecture consists of core parsing utilities (rsql-common), JPA-specific implementations (rsql-jpa), QueryDSL implementations (rsql-querydsl), and Spring Boot starters for easy integration. The library uses the visitor pattern for RSQL parsing and CriteriaBuilder/QueryDSL APIs to construct specifications and predicates.
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.
Eclipse Open VSX is a full-stack, vendor-neutral open-source registry for VS Code extensions, serving as an alternative to the Visual Studio Marketplace. The system comprises three main components: a Java/Spring Boot server that manages extension publishing, security scanning, rate limiting, download analytics, and trusted publishing via OIDC; a React/TypeScript web UI (MUI, TanStack Query) for browsing, searching, and administering extensions; and a Node.js CLI for publishing, verifying, and managing extensions. The server uses PostgreSQL with Flyway migrations, optional Elasticsearch for search, TimescaleDB for time-series download analytics, and Valkey/Redis for caching and rate limiting. Storage is abstracted over local filesystem, AWS S3, Azure Blob, and Google Cloud Storage. The architecture is a monolith with background job processing via JobRunr, and it exposes both a custom REST API and a VS Code Gallery-compatible API for seamless integration with VS Code and other editors.
YAS (Yet Another Shop) is a production-grade, open-source e-commerce platform implemented as a microservices architecture using Java Spring Boot for the backend and Next.js for the frontend (both storefront and admin backoffice). The system is decomposed into ~15 independent microservices (product, cart, order, customer, inventory, payment, promotion, rating, tax, location, media, search, webhook, recommendation, and sample data) that communicate via REST with resilience4j circuit breakers/retries and event-driven patterns using Kafka and Debezium CDC for cross-service data synchronization (e.g., product changes propagate to Elasticsearch for search and PgVector for recommendation). Authentication and authorization are handled via Keycloak with OAuth2/JWT. The architecture includes BFF (Backend For Frontend) gateways using Spring Cloud Gateway and two Next.js frontends. Infrastructure is fully containerized with Docker Compose and Kubernetes Helm charts, with observability via OpenTelemetry, Grafana, Loki, and Tempo. The codebase includes comprehensive unit/integration tests, UI automation tests (Selenium/Cucumber), and CI/CD pipelines per service. While the repository is primarily an application, it incorporates data engineering patterns (CDC, vector embeddings) for the recommendation and search features, giving it a slight hybrid data character. Overall, the code demonstrates solid engineering practices, a well-defined microservice boundary, and several reusable components, though some duplication across services and boilerplate configs exist.
Openrouteservice is a production-grade, open-source routing service built on a forked GraphHopper engine. It exposes a REST API (Spring Boot, JSON/GeoJSON/GPX) for directions, isochrones, matrix calculations, map matching, and graph export, supporting multiple transport profiles (car, foot, bike, wheelchair, heavy vehicle) with extensive customization via weightings (fastest, green, quiet, steepness, heat stress), edge filters (borders, areas, features, traffic), and real-time data integration from PostGIS. Architecturally, the project is modular: `ors-api` handles HTTP concerns and request/response DTOs, `ors-engine` contains the core routing algorithms and GraphHopper extensions, `ors-benchmark` provides Gatling-based load testing and coordinate generation tools, and `ors-test-scenarios` runs containerized integration tests. Advanced features include fast isochrones via graph partitioning (InertialFlow, contraction hierarchies), RPHAST for many-to-many matrices, and core routing with landmarks (ALT). Graph lifecycle management supports remote repository download (HTTP, Minio, filesystem) and hot-reload. While primarily an application, the repository incorporates data research elements: OSM data pipelines for tag filtering and elevation processing, statistical population queries for isochrones, and environmental routing indices (noise, shadow, green) sourced from CSV files. The codebase demonstrates strong engineering practices – modular design, extensive unit/integration tests, property-based testing, and a plugin system for extensible storages – though heavy customization of GraphHopper internals introduces maintenance risks and a moderate technical drift from upstream.
Appsmith is a comprehensive low-code application development platform that enables users to build internal tools, dashboards, and admin panels via a visual editor. The architecture consists of a React/TypeScript frontend (SPA) for the IDE and a Java Spring Boot backend (WebFlux) for business logic and data persistence. It features a robust plugin system for connecting to diverse datasources (SQL, NoSQL, SaaS, AI) and deep Git integration for version control and CI/CD workflows. The system is containerized for deployment and supports both Community and Enterprise editions through feature-flagged code paths.
hsweb-framework is a modular Java backend development framework, not a single deployable application. It is built as a multi-module Maven monorepo providing reactive-first CRUD scaffolding, RBAC/authorization, an OAuth2 authorization server, dynamic datasource switching, reactive caching, access logging, i18n, dictionary/enum support, and file upload services. The code is dominated by Spring Boot auto-configurations, SPI extension points, and reusable controller/service interfaces that applications consume as dependencies. It supports both WebFlux (R2DBC) and WebMVC (JDBC) stacks, with reactive APIs as the primary design direction. Architecturally, the framework centers on hsweb-core (bean utilities, i18n, exceptions, ID generation), hsweb-commons (generic CRUD services/controllers, query helpers, SQL analysis), hsweb-authorization (authentication model, token management, AOP method authorization, OAuth2 granters/authenticators), hsweb-datasource (dynamic schema/table/datasource switching), hsweb-concurrent-cache (ReactiveCache with Guava/Caffeine/Redis backends), hsweb-logging (AOP access logs), and hsweb-system (default user, permission, dictionary, and file modules). Key entry points are Java annotations such as @Authorize, @Resource, @EnableEasyormRepository, @EnableEntityEvent, and interface contracts like ReactiveServiceCrudController and CrudService, which auto-generate REST endpoints for entities. Primary data flows move from HTTP requests through WebFlux/WebMVC controllers into reactive or synchronous CrudService implementations, then through EasyORM repositories to R2DBC/JDBC databases. Authorization flows are layered: token parsing/generation, AuthenticationManager initialization, AOP authorization definition parsing, data-permission handlers, and OAuth2 grant/redirect handling. Entity lifecycle events, cache invalidation, and query rewriting are cross-cutting mechanisms implemented via Spring application events, Reactor context, and JSqlParser-based SQL analysis. Redis is used for token storage and cache synchronization; Caffeine/Guava support local reactive caches. External dependencies include Spring Boot 3.x, Reactor, R2DBC, JDBC, Redis, JSqlParser, and Javassist. The codebase demonstrates strong engineering in isolated utilities like FastBeanCopier, reactive cache invalidation, streaming JSON response writing, and SQL query analysis. However, it carries notable drift: mixed javax/jakarta annotations, deprecated legacy APIs, a coexistence of servlet and reactive paths, some ignored/incomplete tests, and complex compatibility layers around OAuth2 and cache semantics. Overall it is a mature, actively maintained framework with substantial reusable components, though consumers should expect to navigate Chinese-language comments and some legacy baggage.
This is the Spring Tools 4 (STS4) repository, a comprehensive set of IDE tooling for Spring Boot development. It provides language servers (LSP) for Spring Boot (Java, YAML, properties, XML), Concourse CI, BOSH, and Cloud Foundry manifests, along with Eclipse plugins and VS Code extensions. The architecture separates headless language servers (built as Spring Boot applications) from IDE-specific frontends, with shared commons libraries for YAML, Java project indexing, metadata, and live process monitoring via Actuator. The codebase is professional and well-structured but shows signs of organic growth over a decade, with some code duplication between the Eclipse and headless/VS Code paths, deprecated API usage, and developer-specific hardcoded paths. It is actively maintained by VMware/Spring engineering team with strong CI/CD pipelines.
This repository implements a food ordering system using a microservices architecture with four services: customer, order, payment, and restaurant. It employs Domain-Driven Design, clean/hexagonal architecture, and patterns such as Saga for distributed transactions, Outbox for reliable messaging, and CQRS for separating commands and queries. Services communicate asynchronously via Kafka with Avro serialization. The system includes REST APIs for customer and order operations, and uses Spring Boot with JPA for persistence.
WebGoat is a deliberately insecure web application designed for security training, providing hands-on lessons for the OWASP Top 10 vulnerabilities. In production, it operates as a Spring Boot monolith with a modular lesson architecture; each lesson is a self-contained endpoint that simulates a real-world vulnerability (SQL injection, XSS, CSRF, JWT misuse, etc.) and validates the user's attack payload. A companion application, WebWolf, acts as attacker infrastructure (file hosting, JWT encoding/decoding, request logging). The system includes user registration, progress tracking via JPA/Flyway with per-user database schemas, and a Thymeleaf/Backbone.js frontend with multilingual support. External dependencies include H2/HSQLDB, Spring Security, AsciiDoc rendering, and intentionally outdated libraries (e.g., jQuery 2.1.4) to demonstrate specific weaknesses. The architecture is well-structured but carries intentional technical debt for educational purposes. The most reusable components are the WebAuthn support utilities (CBOR, COSE, attestation parsing) and the command execution service, both of which demonstrate non-obvious engineering skill and can be extracted independently.
This repository is the Spring Cloud integration layer for Netflix Eureka, providing both client-side service registration/discovery and an embedded Eureka server. It is a library, not a standalone application, designed to be consumed by Spring Boot microservices. The architecture is a multi-module Maven project with clear separation between client (`spring-cloud-netflix-eureka-client`), server (`spring-cloud-netflix-eureka-server`), and starter modules. In production, it enables Spring Boot applications to automatically register with a Eureka server, discover other services via `EurekaDiscoveryClient` or `EurekaReactiveDiscoveryClient`, and integrate with Spring Cloud LoadBalancer for zone-aware routing. The server module provides a full Eureka registry with a web dashboard, peer replication, and Micrometer-based metrics. The codebase demonstrates strong Spring Boot auto-configuration patterns, including conditional HTTP client selection (Jersey, RestClient, WebClient), health check aggregation, and config server bootstrapping. While actively maintained with a sophisticated release train CI system, the project carries significant technical debt from its long history. It still defaults to the deprecated Jersey HTTP client, relies on an older version of Netflix Eureka (2.0.6), and has several disabled flaky tests. The tight coupling to Netflix's proprietary libraries limits its reusability outside the Spring Cloud ecosystem, but the patterns it demonstrates for service discovery integration are well-crafted and instructive.
This is a Spring Boot starter library that deeply integrates Square's Retrofit HTTP client with Spring Boot's auto-configuration, allowing developers to declare typed HTTP APIs via Java interfaces annotated with `@RetrofitClient`. The library provides a comprehensive set of features: automatic OkHttpClient management, a pluggable interceptor chain (global, network, path-match), configurable retry with exponential backoff and jitter, circuit breaking (via Sentinel or Resilience4j), logging strategies, Micrometer metrics, custom error decoding, and connection pooling. It also supports Spring Boot Actuator for runtime introspection, GraalVM native image/AOT compilation, and reactive call adapters (RxJava 2/3, Reactor). The architecture is modular with clear SPIs for extensibility (e.g., `SourceOkHttpClientRegistrar`, `GlobalInterceptor`, `RetrofitDegrade`, `ErrorDecoder`), and the configuration is annotation-driven with global defaults overridable per-client. The codebase is well-tested with integration tests using MockWebServer, and documentation is provided in multiple languages. However, the tight coupling to specific versions of Retrofit, OkHttp, and Spring Boot introduces moderate technical drift, as some optional dependencies (e.g., Sentinel 1.8.6, Resilience4j 1.7.1) are older. The library is primarily a framework integration rather than a standalone application, but its design patterns serve as a reference for building Spring Boot auto-configuration with complex SPI chains.
This is a monolithic Spring Boot web application built with Kotlin that implements a blog engine. The application serves both HTML pages via Mustache templates and provides a REST API for articles and users. It uses Spring Data JDBC for data access with an H2 database, and includes sample data initialization. The architecture follows standard Spring MVC patterns with controllers handling web and API requests, repositories for data access, and configuration properties for externalized settings. The code demonstrates idiomatic Kotlin usage with extension functions, data classes, and proper null safety.
This repository is a Spring Boot training/courseware package rather than a production service. It consists of five independent, runnable Spring Boot applications under com.kousenit (demo, restclient, persistence, shopping, springai), accompanied by lab workbooks (labs.md, advanced-labs.md), course slides (slides.md), and CI workflows. The code demonstrates current-generation Spring and Spring Boot patterns: MVC and REST controllers, Java records for DTOs, RestClient and HTTP interfaces, JdbcClient and JPA data access, AOP aspects, RFC 7807 exception handling, and Spring AI chat clients. Although the dominant character is application code, it is educational example code, not a deployed system.
This repository contains a full-stack application for AI-powered short drama generation. The system enables users to create drama projects, extract characters and scenes from text using AI models, generate consistent character and scene images, create storyboards, and produce final videos. It manages the entire lifecycle from text input to multimedia output, with real-time task tracking and asset management. The backend is built with Spring Boot (Java 17) and follows a layered architecture with controllers, services, decorators (for Redis caching), facades (for asynchronous persistence), and mappers (using MyBatis-Plus). The frontend is a Vue 3 + Vite application using the Composition API for state management and communicating with the backend via REST APIs and WebSocket for real-time updates. The system integrates multiple technologies: MySQL for primary data storage, Redis for caching, RabbitMQ for asynchronous task processing, MinIO for object storage, Elasticsearch for full-text search, and Qdrant for vector-based context retrieval in storyboard generation. Key architectural patterns include the Strategy pattern for swapping AI model providers, the Decorator pattern for adding cross-cutting concerns like caching, and the Facade pattern for decoupling asynchronous operations. Reusable components include utility classes for Redis, MinIO, and Qdrant operations, as well as Vue 3 composables for global loading state and model configuration. The application demonstrates strong engineering practices in handling complex AI workflows while maintaining modularity and extensibility.
This repository is a production-grade, full-stack enterprise AI agent platform developed by iFlytek (Astron Agent). The system allows organizations to create, configure, deploy, and manage conversational AI agents (bots) with advanced workflow automation, knowledge retrieval (multi-strategy RAG), a plugin ecosystem (including MCP and HTTP tools), and multi-tenant team collaboration. The architecture is polyglot and service-oriented: a Java Spring Boot console backend handles bot lifecycle management, publishing to channels (API, WeChat, Feishu, marketplace), RBAC permissions, enterprise spaces, and notification systems. Python FastAPI core services power the workflow engine (20+ node types including LLM, code, decision, memory, knowledge), agent runtime with skill sandbox execution, knowledge indexing and retrieval, and plugin integrations (link server, RPA, MCP). A Go service manages tenant authentication and app key verification. The React + TypeScript frontend provides an interactive console for workflow design, model management, resource management (databases, knowledge bases, skill files), trace logs, and chat interfaces. External dependencies include multiple LLM providers (iFlytek Spark, OpenAI, Anthropic, Google, DeepSeek), MySQL, Redis, Kafka, S3-compatible storage, and Casdoor for SSO. The codebase demonstrates professional engineering with test coverage (JUnit, pytest, Jest), Flyway and Alembic database migrations, CI/CD pipelines, and a modular design using strategy, factory, and AOP patterns. However, it shows signs of complexity from polyglot maintenance, some duplicated frontend components, and legacy credential handling that has been addressed through targeted migration fixes. Overall, it is a well-maintained, actively developed platform suitable for mid-to-large enterprise deployments.
Apache ShardingSphere ElasticJob is a distributed job scheduling framework providing elastic sharding, failover, misfire handling, and lifecycle management. It is a Java library that can be embedded in applications or used via Spring Boot auto-configuration. The system coordinates jobs across multiple nodes using a registry center (ZooKeeper, etcd, Nacos, or in-memory). It supports multiple job types (simple, dataflow, script, HTTP) and provides RESTful admin APIs, event tracing, and error notification. The architecture is modular with clear SPI-based extensibility for job executors, error handlers, tracing listeners, and registry center providers. The codebase is well-engineered with extensive tests, but retains some legacy integration paths (Spring XML namespace) and tight coupling to ZooKeeper in core modules.