GStones/moke-kit
This system is a modular Go application framework that provides a unified infrastructure for managing server lifecycles, data persistence, and messaging. It integrates gRPC, HTTP, and WebSocket services with a pluggable architecture for NoSQL (MongoDB, Redis) and SQL (GORM) storage, alongside support for multiple message queue backends (NATS, Kafka, etc.). The codebase emphasizes testability through extensive mock implementations and dependency injection, enabling secure, observable, and scalable service development.
54.9
Adequate · 3 August 2026
4.7k
lines of production code
Go
primary language
2
bus factor · 6 authors in all
3
measurements over time
How it got here
2023 · infrastructure and service layer expansion
The project significantly expanded its internal architecture by introducing a modular, dependency-injection-based framework using Uber fx. This period focused on building out core infrastructure components, including a unified server interface with connection multiplexing, a structured logging system, and a comprehensive message queue abstraction. Additionally, the codebase established robust data access layers for both SQL (GORM) and NoSQL (MongoDB, Redis) operations, supported by centralized error handling and utility packages.
24 changes
2024–2025 · Agones integration and infrastructure modularization
This period focused on integrating the Agones game server framework by introducing SDK wrappers, interfaces, and mock implementations to support local development and testing. Concurrently, the codebase was refactored to adopt a modular, dependency-injection-based architecture, adding support for message queues, authentication, and secure gRPC communication.
14 changes
Survey your own repository
GStones/moke-kit was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.
About this page
- The description of this project is derived from its own commit history, not from its README.
- The score is its highest published measurement, taken on 3 August 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit 51decbce44 — the exact code this score is about.
- Scored under rubric rubric-2026.08.19. Score the same commit under that rubric and you get the same number.