This is a full-stack web application starter kit combining Angular (frontend) and Spring Boot (backend) with JWT-based authentication. The system provides user registration, login, role-based access control (USER/ADMIN), and protected API endpoints. The frontend communicates with the backend via RESTful APIs, with authentication handled through JWT tokens stored in cookies. The architecture follows a standard client-server pattern with clear separation of concerns: Angular handles UI presentation and user interactions, while Spring Boot manages business logic, data persistence, and security. Key features include route guards for client-side protection, custom JWT filters for server-side authentication, and centralized service layers for API communication.
The Pentaho Platform is the core backend for the Pentaho Business Analytics server. In production, it serves as a content repository (JCR/Jackrabbit), authentication/authorization system, scheduler (Quartz), and a plugin-based execution engine for BI actions (reports, OLAP, data integration). The system is a monolithic Java EE application deployed on Tomcat, using Spring for dependency injection, Hibernate for persistence, and GWT for the legacy user console. It provides REST and SOAP APIs for repository management, security administration, and job scheduling. The codebase is organized into modules (api, core, extensions, repository, scheduler, user-console) and relies on external libraries such as Apache Jackrabbit, Quartz, Mondrian, Kettle, and Spring Security. Architecturally, the platform is built around a central static service locator (PentahoSystem) and a large set of interfaces for actions, components, and services. It supports multi-tenant repository paths, pluggable authentication (LDAP, JDBC, memory), and a rule-based authorization system. The platform is functionally comprehensive but carries significant technical debt: deprecated interfaces, mixed JUnit versions, outdated front-end technologies (Dojo, GWT), and over-engineered exception hierarchies. Some modules (e.g., authorization decisions, cache expiration, file content decoration) are well-designed and potentially reusable.
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 curated collection of Java interview questions and answers, organized by topics such as Core Java, Collections, Concurrency, Spring, Hibernate, SQL, and more. It also includes several small, self-contained Java projects that demonstrate specific concepts: a custom Stream API implementation (custom-stream), a deadlock example (deadlock), a set of LeetCode algorithm solutions (leetcode-221-maximal-square), and a flawed code review snippet (review). The primary value is the extensive markdown documentation with links to external resources, making it a useful study aid for Java interview preparation. The code examples are educational but not production-grade; the custom-stream project is the most notable for illustrating the internal pipeline pattern of Java Streams. The repository is static and has not been actively updated in some time, though the content remains relevant for many core Java topics.
YapAnimator is a physics-based animation library for iOS, tvOS, and macOS, written in Swift 3.1. It provides a generic `YapAnimator<T>` class that animates any value conforming to the `Animatable` protocol by decomposing it into an array of doubles and applying spring physics integration with a fixed 1/240s timestep. The library includes a convenience layer (`YapAnimatedLayer`) attached to `CALayer` via associated objects, enabling one-liner animations of layer properties like position, bounds, opacity, transform, etc. The core engine runs on a display link (CADisplayLink on iOS/tvOS, CVDisplayLink on macOS) and manages all active animators. The repository is explicitly archived and no longer maintained, with Swift 3.0/3.1 dependencies and no updates since 2017.