mxdldev / spring-cloud-flycloud
🔥🔥🔥FlyClould 微服务实战项目框架,在该框架中,包括了用 Spring Cloud 构建微服务的一系列基本组件和框架,对于后台服务框架的搭建有很大的参考价值,大家可以参考甚至稍加修改可以直接应用于自己的实际的项目开发中,该项目没有采用Maven进行项目构建,Maven通过xml进行依赖管理,导致整个配置文件太过臃肿,另外灵活性也不是很强,所以我采用Gradle进行项目构建和依赖管理,在FlyTour项目中我们见证了Gradle的强大,通过简单的一些配置就可以轻松的实现组件化的功能。该项目共有11个Module工程。其中10个位微服务工程,这10个微服务工程构成了一个完整的微服务系统,微服务系统包含了8个基础服务,提供了一整套微服务治理功能,他们分别是配置中心module_config、注册中心module_eureka、认证授权中心module_uaa、Turbine聚合监控服务module_monitor、链路追踪服务module_zipken、聚合监控服务module_admin、路由网关服务module_gateway、日志服务module_log。另外还包含了两个资源服务:用户服务module_user和blog服务module_blog,另外还有一个common的Module,为资源服务提供一些一本的工具类
- Stars
- 1,579 stars
- Forks
- 438 forks
- Language
- Java
- License
- APACHE-2.0
- Created
- Feb 14, 2019
- Last push
- Jun 29, 2020
- Updated
- Nov 9, 2026
Admitted to the Repository Index on Nov 12, 2026: 1,579 stars on 2026-11-12.
Star History
111 days recorded, Jul 27, 2026 – Nov 14, 2026 (UTC). Net change +4 stars.
The star count of each day is the latest count minus the net stars of the later days.
Add this Star History to a README
The images follow the light or dark theme of the page that shows them, and update every hour.
Add ?theme=light or ?theme=dark
to the chart address to keep one theme.
Star History chart
[](https://awesomerepos.com/mxdldev/spring-cloud-flycloud) Badge
[](https://awesomerepos.com/mxdldev/spring-cloud-flycloud) Timeline
It gained stars on 4 of the 111 days recorded since Jul 27, 2026.
Its largest 7 days were Oct 16, 2026 to Oct 22, 2026: 2 stars.
In the 30 days to Nov 14, 2026 it got 2 stars, 100% more than in the 30 days before.
It had 1,575 stars before Jul 27, 2026 and has 1,579 stars now: 3,421 fewer than 5,000.
- Created on the Repository Host
- Release v2.0.0
- Release v1.0.0
- Release v2.1.0
- Release v3.0.0
- Release v2.2.0
- Latest push
- Largest star day recorded: +1 stars
- +1 stars in one day
- +1 stars in one day
- Entered the Repository Index: 1,579 stars on 2026-11-12
The timeline comes from the creation date and the releases on the Repository Host, the Admission, the Star History, and the Observations. Star milestones show only when the Star History records the day. The list shows up to 5 stable releases from the latest 10 releases recorded. When none of them is stable, one item counts the pre-releases. On the chart of net stars each day, a solid line marks each recorded release.
Forks and pushes
From 3 Observations, Nov 13, 2026 – Nov 15, 2026. Forks 0. AwesomeRepos saw a new push on 0 of 2 days.
- Nov 14, 2026: no new push
- Nov 15, 2026: no new push
A filled day: the last push time changed since the Observation before it.
Health facts
Measured facts in four separate dimensions, each with a date and a source. AwesomeRepos does not add them into one score. AwesomeRepos reads the weekly commits, the changelog, and the community files each week for the 5,000 visible repositories with the most stars and for each rising repository. How AwesomeRepos defines each check
Copies a prompt for a coding agent. It has 1 task for the maintainers of mxdldev/spring-cloud-flycloud.
Improve the Health Facts of the GitHub repository mxdldev/spring-cloud-flycloud. AwesomeRepos measures facts about how a repository is maintained, released, secured, and documented. Its page for this repository is https://awesomerepos.com/mxdldev/spring-cloud-flycloud. A change to the repository can improve each of the item below. Each item gives the measured fact or score, and a task. 1. A release in the last 365 days Fact: Newest release v3.0.0 on 2020-03-23, 2427 days ago. 0 releases in the last 365 days. Rule: The newest published GitHub release (a pre-release counts; a draft does not) is 365 days old or less. A repository that publishes only tags, or only to a package registry, has no GitHub release. The release refresh reads the 10 newest releases after each push to the repository, and at least each 30 days. The index refresh reads the date of the last push each day. Task: Prepare a release, but do not publish it. Find the changes since the newest release, propose the next semantic version and the release notes, and ask me to publish the GitHub release. If nothing changed since the newest release, skip this item. If the project publishes only to a package registry, add a CI step that also makes a GitHub release for each version tag. Rules for this work: - Each file must be true for this project. Do not copy text that does not apply to it. - Do not choose a licence, a contact, or a release version for me. Ask me. - Do not publish a release, change a repository setting, or push to the default branch. Make the changes on a new branch. - Keep each change small, and run the checks of this repository before you finish. - At the end, list each item as DONE, SKIPPED (with the reason), or NEEDS A DECISION (with the question). AwesomeRepos reads these facts again in its next scan. The definitions of the checks: https://awesomerepos.com/health-facts
Maintenance
1 of 4 checks (2 without data)-
Yes: Not archived
GitHub does not mark the repository as archived. Source
-
No: A push in the last 90 days
Last push on 2020-06-29, 2330 days ago. Source
-
No data: Commits in the last 13 weeks
No data: AwesomeRepos has not read the weekly commits.
-
No data: Commits in 26 or more of the last 52 weeks
No data: AwesomeRepos has not read the weekly commits.
Releases
1 of 3 checks (1 without data)-
No: A release in the last 365 days
Newest release v3.0.0 on 2020-03-23, 2427 days ago. 0 releases in the last 365 days. Source
-
Yes: The newest release tag is a semantic version
The newest release tag is v3.0.0. Source
-
No data: A changelog file at the root
No data: AwesomeRepos has not scanned this repository.
Security practice
0 of 1 check (1 without data)-
No data: A security policy
No data: AwesomeRepos has not scanned this repository.
AwesomeRepos has not asked OpenSSF Scorecard about this repository.
Community files
1 of 3 checks (2 without data)-
Yes: A licence
GitHub finds the licence APACHE-2.0. Source
-
No data: A contributing guide
No data: AwesomeRepos has not scanned this repository.
-
No data: A code of conduct
No data: AwesomeRepos has not scanned this repository.
Observations
Latest Observation, Nov 15, 2026: 1,579 stars, 438 forks, last push Jun 29, 2020, not archived. One of 3 Observations since Nov 13, 2026.