limingfan2016 / game_service_system
从0开始开发 基础库(配置文件读写、日志、多线程、多进程、锁、对象引用计数、内存池、免锁消息队列、免锁数据缓冲区、进程信号、共享内存、定时器等等基础功能组件),网络库(socket、TCP、UDP、epoll机制、连接自动收发消息等等),数据库操作库(mysql,redis、memcache API 封装可直接调用),开发框架库(消息调度处理、自动连接管理、服务开发、游戏框架、服务间消息收发、消息通信等等),消息中间件服务(不同网络节点间自动传递收发消息)等多个功能组件、服务,最后完成一套完整的服务器引擎,基于该框架引擎可开发任意的网络服务。 主体架构:N网关+N服务+N数据库代理+内存DB(Redis、MemCache)+Mysql数据库,基于该架构可建立集群,稳定高效的处理大规模、高并发消息。
- Stars
- 1,116 stars
- Forks
- 439 forks
- Language
- C++
- License
- Not reported
- Created
- Jun 5, 2016
- Last push
- Jul 5, 2022
- Updated
- Oct 30, 2026
Admitted to the Repository Index on Nov 14, 2026: 1,116 stars on 2026-11-14.
Star History
181 days recorded, May 20, 2026 – Nov 16, 2026 (UTC). Net change +7 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/limingfan2016/game_service_system) Badge
[](https://awesomerepos.com/limingfan2016/game_service_system) Timeline
It gained stars on 7 of the 181 days recorded since May 20, 2026.
Its largest 7 days were May 25, 2026 to May 31, 2026: 1 star.
In the 30 days to Nov 16, 2026 it got 1 star, 50% fewer than in the 30 days before.
It had 1,109 stars before May 20, 2026 and has 1,116 stars now: 3,884 fewer than 5,000.
- Created on the Repository Host
- Latest push
- Largest star day recorded: +1 stars
- +1 stars in one day
- +1 stars in one day
- Entered the Repository Index: 1,116 stars on 2026-11-14
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 15, 2026 – Nov 17, 2026. Forks 0. AwesomeRepos saw a new push on 0 of 2 days.
- Nov 16, 2026: no new push
- Nov 17, 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 2 tasks for the maintainers of limingfan2016/game_service_system.
Improve the Health Facts of the GitHub repository limingfan2016/game_service_system. AwesomeRepos measures facts about how a repository is maintained, released, secured, and documented. Its page for this repository is https://awesomerepos.com/limingfan2016/game_service_system. A change to the repository can improve each of the 2 items below. Each item gives the measured fact or score, and a task. 1. A release in the last 365 days Fact: No GitHub release (read on 2026-11-14). 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. 2. A licence Fact: GitHub finds no licence. Rule: GitHub finds a licence file. When GitHub cannot name the licence, the fact says so. Task: Ask me which licence to use. Do not choose one yourself. Then add the standard licence text as LICENSE at the root, so that GitHub can name the licence. Do not change the terms. Fill in only the fields of the template (for example the year and the copyright holder), and ask me for a value that you cannot verify. 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 2022-07-05, 1596 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
0 of 3 checks (2 without data)-
No: A release in the last 365 days
No GitHub release (read on 2026-11-14). Source
-
No data: The newest release tag is a semantic version
No data: no release.
-
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
0 of 3 checks (2 without data)-
No: A licence
GitHub finds no licence. 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 17, 2026: 1,116 stars, 439 forks, last push Jul 5, 2022, not archived. One of 3 Observations since Nov 15, 2026.