# bage2014/study: a shelf of runnable Java stack notes, one module per topic

> The study repository is a personal full-stack engineer's notebook organised as a directory of small Maven projects, covering Spring, Spring Boot, security and single sign-on, caching, messaging, databases and distributed patterns, each with theory and a worked example. It suits a Java developer who wants a runnable reference rather than prose, and it is a personal collection rather than a maintained framework.

**bage2014/study** — Java全栈工程师学习笔记；Spring、shiro、CAS、oauth2单点登录；cache 、Redis; web 安全及解决思路；redis、mq、quartz、docker；Docker各种组件实践等；mybatis、spring、spring boot实践；分布式锁；基于分库分表等等；Java full-stack engineer study notes; Spring, shiro, CAS, oauth2 single sign-on; cache, Redis; web security and solutions; redis, mq, quartz, docker; Docker various component practices, etc.; 

- Repository: https://github.com/bage2014/study
- Stars: 648 · Forks: 113
- Language: Java
- License: not declared
- Published: 2026-10-21 · Updated: 2026-10-21 · Language: en
- Canonical page: https://hysenlabs.com/projects/bage2014-study

## A notebook made of small Maven projects

The repository describes itself as a comprehensive technical study repository containing the various knowledge points and practice cases a Java full-stack developer needs, and the readme is clear that each submodule is an independent study unit containing theory and code practice.

The structure is the interesting part, because it is not a documentation site. The top-level entries are directories, each one a self-contained project: study-java, study-spring-boot, study-redis, study-mybatis, study-shiro-web, study-jwt, study-dubbo, study-activemq, study-clickhouse and a long tail of others, alongside a root pom.xml, a config/ directory, an arthas-output/ directory, and a pair of starter modules named bage-spring-boot-starter-ping and bage-spring-boot-starter-ping-test.

So the unit of the repository is a working module with its own build file, not a markdown page. A developer looking for how to wire Spring Security into a Boot application opens a directory and reads code, and the readme's own description of the Java basics modules confirms the pattern: study-java for core knowledge, study-java11 for the new language features, study-lombok for the annotation processor, study-servlet for the servlet basics, study-bytebuddy for bytecode manipulation and study-cglib for dynamic proxies.

The audience is a Java developer learning the stack, or one who already knows it and wants a working example to copy from. The English version of the readme is at README.en.md, alongside README_Template.md, so the same index exists in two languages.

## Ten topic groups, and a security section that is unusually broad

The readme groups the modules into ten categories, and the shape of that grouping says what the author was trying to cover.

The first groups are the core language and the framework stack: Java basics, data structures and algorithms, Spring Framework, Spring Boot, databases, caching, message queues, distributed systems and microservices, security and authentication, and tools and testing.

The Spring Framework group is split by configuration style rather than by feature, with study-springmvc-java, study-springmvc-xml and study-springmvc-nowebxml as three separate modules for the same framework. The Spring Boot group is longer still, with modules for H2, JPA, Docker, security, testing, parameter validation, WebSocket, ELK logging, Zipkin tracing, call chains, multiple data sources, dynamic data source switching, and an OAuth2 auth server.

The security and authentication group is the widest, with ten modules: Spring Security, a Shiro tutorial, Shiro web, a CAS client, a CAS server, OAuth, JWT, JWE, SAML, and an SSO OAuth2 server. That spread is the point of the group. Single sign-on is the recurring theme across it, and the repository covers it from several angles, with both a CAS client and a CAS server, an OAuth module next to OAuth2 and JOSE modules, and SAML and SSO OAuth2 server modules alongside Spring Security itself.

The distributed group follows the same pattern of covering the same problem with different tools: Dubbo, Spring Cloud Circuit Breaker, Hystrix, Resilience4j and Sentinel, plus Spring Session and shared session modules. And the database group includes MyBatis, MyBatis Plus, MongoDB, OceanBase, ClickHouse, Canal for data synchronisation, and a module for sharded databases and tables, which is a considerably harder topic than the rest.

## The module links point at the author's own machine, which breaks the index

There is a detail in the readme tables that undercuts the whole index, and it is worth pointing out because it will cost you time.

Every module link is a local file URL rather than a relative path. The pattern is file:///Users/bage/bage/github/study/ followed by the module name, so the entry for the Redis module points at file:///Users/bage/bage/github/study/study-redis, and the entry for the CAS client points at file:///Users/bage/bage/github/study/study-cas-client. Those paths exist on the author's machine and on nobody else's, so none of the links in the readme resolve for a reader who clones the repository.

The format is visible in the raw table, where each entry is a local file URL rather than a relative path:

```markdown
| [study-redis](file:///Users/bage/bage/github/study/study-redis) | Redis |
| [study-cas-client](file:///Users/bage/bage/github/study/study-cas-client) | CAS 客户端 |
```

The content is still there. The directories are in the repository, and the table still tells you what each one covers, so the index remains usable as a table of contents. It just cannot be clicked, and the description column is written in Chinese for every entry.

The fix is small if you want the links to work locally: rewrite them as relative paths pointing at the directories, which is what the module names already are. That is a pull request someone could send.

There is a second mismatch, and it runs the other way. The top-level directory listing contains modules the readme tables never mention, including a cluster of study-ai-* directories, study-ai-mcp-client, study-ai-mcp-server and study-ai-skills, alongside study-axon, study-calcite, study-call-trace, study-code-generator, study-crawler, study-cryption and study-ddd. The readme's own project description mentions backend development, frontend techniques, databases, middleware and AI applications, and the directory listing shows that the AI work has grown well past what the tables document.

## How to actually use the repository

There is no install command, and there is no need for one. Each module is a separate Maven project with its own pom.xml, and the root pom.xml aggregates them, so the workflow is clone, open the directory you care about, and build that module.

The repository also carries a root config/ directory, which is what you would expect to hold the shared configuration for a set of small projects, and an arthas-output/ directory, which is the working directory for Arthas, the Java diagnostic tool that has its own module, study-arthas. A .gitignore, a .gitignore.md and a .traeignore sit alongside the readmes.

The size of the tree is the practical constraint. The directory listing runs to more than a hundred entries in the visible portion, and each is a project with its own dependencies, its own configuration and its own version of the framework it teaches. Cloning the whole thing and trying to build everything at once is the approach most likely to fail, because the modules were written at different times against different Spring Boot and Spring versions.

A better pattern for a reader is to pick the single concept you are stuck on, open that one directory, build it, and read the code alongside the notes. The grouping in the readme is the right index for that, even with the broken links.

## Licence, activity, and what this collection is not

The licence field is not identified in the project data, and the repository entries do not obviously include a licence file at the top level, so the terms are not stated where you would look for them. The GitHub licence badge that would normally carry that information is not part of the visible readme either. For a repository of study code that you might copy a snippet out of, that is a gap worth raising with the author rather than working around.

On activity, the repository is not archived and the last push was on 2026-10-19, and there are no GitHub releases, so the version history is whatever the individual module build files record. The recent addition of the study-ai-* directories, including MCP client, MCP server and skills modules, suggests the AI work is where the current effort is going.

It is worth being clear about what this is not. It is not a framework, and nothing in it is designed for reuse as a dependency. It is not a course, because there is no ordering, no exercises and no assessment. It is not a curated list of external resources, because the code is written in the repository rather than linked out. The design principle that a full-stack engineer in 2026 would recognise is that the third one is what most people want, and this is not it.

What it is, and what makes it worth cloning, is a large set of small, specific, working demonstrations. A working Spring Boot module with an ELK stack wired in, or a CAS client and a CAS server talking to each other, or a sharded database setup, is a genuinely useful thing to have on disk when you are implementing that piece for the first time and the documentation is thin. The gap in the readme is the gap in most personal notebooks: nobody has turned a working folder into a teaching path, and the readme's table is the closest thing to a map.

## Conclusion

The study repository fits a Java developer who wants a runnable example of one concept at a time, a pattern that works for a teaching collection and poorly for a reference anyone depends on. Before cloning it, pick the two or three modules you actually need rather than the whole tree, expect to fix the build as the framework versions it targets age, and treat the module list in the readme as a subset, since the top-level directory holds considerably more than the tables document.

## FAQ

### What is the bage2014/study repository?

It is a comprehensive technical study repository for Java full-stack engineers, organised so that each submodule is an independent study unit containing theory and code practice. The modules cover Java fundamentals, data structures, Spring and Spring Boot, databases, caching, message queues, distributed systems, security and single sign-on, and tooling and testing.

### How do I build the modules in the study repository?

There is no install step. Each module is a separate Maven project with its own pom.xml under the root pom.xml, so the workflow is to clone the repository, open the directory for the concept you want, and build that module. A root config/ directory holds shared configuration and the arthas-output/ directory is the working directory for the Arthas diagnostics module.

### What does the study repository cover for security and single sign-on?

The security and authentication group has ten modules: Spring Security, a Shiro tutorial, Shiro web, a CAS client, a CAS server, OAuth, JWT, JWE, SAML, and an SSO OAuth2 server. The distributed group similarly covers Dubbo, Spring Cloud Circuit Breaker, Hystrix, Resilience4j, Sentinel, Spring Session and shared session.

### Why do the module links in the study readme not work?

They are written as local file URLs pointing at the author's own machine, in the form file:///Users/bage/bage/github/study/ followed by the module name, so they resolve nowhere else. The directories are still in the repository, so the tables work as a written index, but the links themselves need rewriting as relative paths to be clickable.

### Is the study repository maintained and licensed?

The repository is not archived and the last push was on 2026-10-19, with no GitHub releases published, and a cluster of recently added study-ai-* modules. The licence is not identified in the project data and no licence file is obvious at the top level, so the terms should be confirmed with the author before copying code out of it.

## Sources

- [bage2014/study on GitHub](https://github.com/bage2014/study)
- [Issues](https://github.com/bage2014/study/issues)
- [README](https://github.com/bage2014/study/blob/master/README.md)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/bage2014-study