// the find
zlt2000/microservices-platform
基于SpringBoot2.x、SpringCloud和SpringCloudAlibaba并采用前后端分离的企业级微服务多租户系统架构。并引入组件化的思想实现高内聚低耦合，项目代码简洁注释丰富上手容易，适合学习和企业中使用。真正实现了基于RBAC、jwt和oauth2的无状态统一权限认证的解决方案，面向互联网设计同时适合B端和C端用户，支持CI/CD多环境部署，并提供应用管理方便第三方系统接入；同时还集合各种微服务治理功能和监控功能。模块包括:企业级的认证系统、开发平台、应用监控、慢sql监控、统一日志、单点登录、Redis分布式高速缓存、配置中心、分布式任务调度、接口文档、代码生成等等。
A Spring Cloud microservices reference platform targeting Chinese enterprise developers — covers auth (Spring Authorization Server + OAuth2/JWT), multi-tenancy, RBAC, service mesh via Nacos/Sentinel, and a full observability stack (ELK, SkyWalking, Grafana). It's not a library you pull in; it's a runnable template you fork and extend. Aimed at teams that want a pre-wired architecture they can drop business logic into.
The auth layer is the real value here — Spring Authorization Server with custom grant types (mobile, OpenId, password+code) on top of stateless JWT is non-trivial to wire correctly and this does it properly. The commons starters (zlt-auth-client-spring-boot-starter, zlt-redis-spring-boot-starter, etc.) are genuinely reusable isolation points rather than dumping everything in one module. The observability setup is complete out of the box — SkyWalking for APM, ELK for logs, Grafana/Prometheus for metrics, plus a slow-SQL monitor — most similar projects ship one of these, not all four. Multi-tenant app isolation is baked into the data model from the start, which is far easier than retrofitting it.
Spring Cloud 2022.x still pins Elasticsearch 7.x when 8.x has been out for years — the ES client API changed significantly and that's a real migration cliff. Documentation is almost entirely in Chinese with no English equivalent beyond a stub README, which walls off non-Chinese contributors and makes it hard to evaluate architectural decisions from the outside. The repo history shows the last meaningful push was April 2025 on the master branch, but it's unclear whether it's maintained or effectively archived — issues and PRs aren't visibly triaged. Zuul is still referenced in the topics even though the gateway is now Spring Cloud Gateway — the leftover reference suggests the project's own metadata hasn't been cleaned up, which doesn't inspire confidence in internal consistency.