spring-boot-quick: a Chinese Spring Boot module sampler with a README that oversells it

One Maven reactor holding dozens of unrelated examples

The repository is not an application. It is a Maven reactor with roughly fifty-four `quick-*` directories, each a self-contained Spring Boot project demonstrating one library or one pattern. The GitHub description lists the inventory in a run-on sentence: RabbitMQ with delayed queues, Kafka, JPA, Redis, OAuth2, Swagger, JSP, Docker, k3s, k3d, k8s, a MyBatis field-encryption plugin, global exception handling, logging, multi-module development, multi-environment packaging, caching, a crawler, JWT, GraphQL, Dubbo, ZooKeeper and async processing.

The topics metadata echoes that list, adding assembly, druid, elasticsearch, hbase, sse and spark. Read together, the picture is a personal notebook that grew for years: `quick-async`, `quick-batch`, `quick-camunda`, `quick-flowable`, `quick-liteflow`, `quick-monitor-thread`, `quick-img2txt`, `quick-hmac`, `quick-i18n`. Nobody designed this as a framework. It is a developer working through a technology list, committing each spike as its own directory. That framing matters for how you use it, because it predicts exactly what you will and will not find inside a module.

There are no GitHub releases attached to the repository. The default branch is `master` rather than `main`, and the last push was on 2026-05-16, so the work is still happening, just without versioned artifacts.

Cloning the repo and building one module at a time

The prerequisites are Java 8 or newer, Maven 3.6 or newer, and Git. The quick start is three commands:

git clone https://github.com/vector4wang/spring-boot-quick.git
cd spring-boot-quick

The README then offers two different build strategies, and the second one is the sensible one. `mvn clean install -U` at the root builds the entire reactor, which means resolving every dependency for every example: message brokers, MongoDB drivers, HBase, Dubbo, Flowable, Camunda. For a look at one module, the README suggests changing into its directory and building there.

Running a module needs no more than the standard Spring Boot Maven goal, and the README pairs it with a URL so you know what success looks like. For the MyBatis and Druid example it points at a health endpoint:

cd quick-mybatis-druid
mvn spring-boot:run

The same three-step shape is repeated for the Swagger module at `http://localhost:8080/swagger-ui.html` and for the JWT module. That consistency is the one genuinely good thing about the quick start: every sample is a `mvn spring-boot:run` away from a browser tab, and none of them needs a Docker Compose file to start.

The README module map and the directory tree disagree

The README advertises 80+ production-ready modules, and its architecture section prints a directory tree with a `# Foundation & Dependency Management` comment for `quick-platform`, then groups modules under headings for databases, message queues, security, web, caching, microservices and infrastructure.

The repository's actual top-level listing tells a different story. There are about fifty-four `quick-*` directories, plus `mybatis-crypt-plugin`, `mybatis-crypt-plugin-test`, `nacos-common-config`, `images/`, `pom.xml`, `README.md` and a `.travis.yml`. Several modules named in the README's tree do not appear there: no `quick-platform`, no `quick-redis`, no `quick-swagger`, no `quick-shiro`, no `quick-shiro-cas`, no `quick-rocketmq`, no `quick-rest-template`, no `quick-saturn`, no `quick-starter`, no `quick-vw-crawler`. Conversely the tree contains directories the README diagram omits, including `quick-camunda`, `quick-flowable`, `quick-liteflow`, `quick-i18n`, `quick-okhttp`, `quick-oss`, `quick-mail` and `quick-framework`.

Both facts are true at once: the README describes a structure and the repository holds a different one, and neither author nor reader is wrong about their own snapshot. The practical test takes ten seconds. Clone it and run `ls`, or browse the tree on GitHub, and reconcile against the diagram before you plan anything around it. Note in particular that the quick start tells you to `cd quick-swagger` while the top-level listing has no directory of that name, so treat every command in the README as something to verify against the directory you are actually in.

An Anti 996 badge with no license file behind it

The README carries a badge reading `License: Anti 996`, and the Chinese title block references the same idea. GitHub reports no license for this repository, and the top-level listing contains no LICENSE file, which means the code sits under default copyright rather than under any license text you could point to. Those two statements cannot both be a grant of permission.

That is worth taking seriously if you intend to copy anything. An open source license is what makes reuse lawful; a badge asserting a stance is not a license, and default copyright is the most restrictive setting there is. The actionable check is simple and does not require legal interpretation: look for a LICENSE file at the repository root, and if there is none, treat the code as read-only reference. Read it to understand a wiring pattern, then write your own version.

The homepage in the repository metadata is `http://blog.wangxc.club`, an author blog rather than project documentation. There is no wiki and no docs site listed, so module-level explanation has to come from the per-module README files the main page links to, such as `quick-mybatis-druid/README.md` and `quick-jwt/README.md`.

Pinned to Spring Boot 2.3.4, a line from 2020

The README badges and the technology table both name Spring Boot 2.3.4.RELEASE, Java 8+, Spring Cloud Alibaba 2.2.5.RELEASE, Apache Dubbo 2.7.11, MyBatis 3.5.6 and Shiro 1.9.1. These are real version numbers, and they date the repository precisely. Spring Boot 2.3.4 shipped in the middle of 2020; the 2.x line as a whole has been out of community support for years.

That has a direct effect on what the samples teach. Configuration idioms change across Spring Boot generations: the `spring.datasource` property namespaces, the actuator endpoint paths, the Swagger dependency choices, and the way OAuth2 is configured all moved between 2.x and 3.x. Copying a sample wholesale into a current project can mean copying code that no longer binds. Use the modules for the shape of the wiring, then check each annotation, property key and starter name against the documentation for the Spring Boot line you are actually on.

One smaller inconsistency worth noting: the prerequisites section asks for Maven 3.6+, while the tools row of the technology table lists Maven as `2.7+`. The prerequisite is the one to follow, since the reactor and Spring Boot plugins both assume Maven 3.

What it replaces, and what it does not

The honest comparison is against other Chinese Spring Boot example collections and against Spring's own guides. Where this repository wins is coverage of the parts that are annoying to wire: Druid connection pool configuration, multi-datasource setup, RabbitMQ delayed queues, Dubbo with Nacos registration, global exception handling, assembly-based multi-environment packaging. Those are the directories with real accumulated friction in them, and they are the reason to keep the repository around.

Where it loses is depth and currency. Every module is a demonstration, not a system, so there is no error handling strategy, no observability beyond `quick-monitor-thread`, no test suite worth the name, and no upgrade path. The `.travis.yml` at the root suggests continuous integration was configured once; the tests it would have run are not visible in the top-level listing. If you are learning Spring Boot from scratch, the official guides and reference documentation will teach you current, supported patterns faster than a 2020 snapshot. If you are an experienced developer who needs one specific wiring recipe, this repository is faster than writing it from scratch.

The `quick-archetype` and `quick-maven-plugin` directories suggest the author intended some scaffolding, and `nacos-common-config` suggests configuration was meant to be centralised rather than duplicated per module. Neither is obviously finished. Treat any intent expressed in directory names as unverified until you open the directory.

Editorial conclusion

This repository earns its place as a lookup shelf rather than a course. You open one module, copy the wiring for a single library, and close the tab; nothing here is meant to run as one system, and the module list in the README will not match what you find on disk. Two things decide whether it is usable for you at all: there is no license file, so the code is not legally yours to reuse, and the pinned Spring Boot 2.3.4 line is long past its support window, so every sample is a snapshot of 2020-era configuration. Start by cloning and listing the top-level directories yourself rather than trusting the architecture diagram, then read the module you actually need and judge it against current Spring Boot documentation.

Frequently asked questions

Official sources

1. Issues
2. Project website
3. README
4. vector4wang/spring-boot-quick on GitHub