Tochemey/ego
eGo is an actor-based distributed systems framework built on top of Go-Akt, providing primitives for event sourcing, durable state, and projections. The system manages the full lifecycle of actors, including cluster discovery, remoting, and supervision, while offering extensible interfaces for persistence, encryption, and event streaming. It supports multiple data stores and message brokers, enabling developers to build scalable, observable applications with robust error handling and state management.
70.2
Strong · 3 August 2026
13k
lines of production code
Go
primary language
2
bus factor · 7 authors in all
3
measurements over time
How it got here
2023 · Architectural consolidation and extensibility
The codebase was refactored to shift from a monolithic framework to a meta-framework built on Go-Akt, removing internal implementations of datastores and aggregates to encourage plugin-based extensions. Concurrently, the project expanded its feature set by introducing a pub/sub event stream, configurable projection recovery policies, and updated protobuf schemas to support sharding and encryption.
11 changes
2024 · Persistence and concurrency infrastructure
This period focused on establishing the core persistence and concurrency abstractions, introducing interfaces for state, events, and offsets, alongside lock-free data structures. The team also built out the testing ecosystem with mock generators and in-memory stores, while providing a Kubernetes deployment example to demonstrate the new capabilities.
7 changes
2025–2026 · extensibility and encryption support
The project expanded its architecture to support external event streaming via Kafka, NATS, Pulsar, and WebSocket, while introducing a centralized extension registry for state management and telemetry. This period also added robust encryption capabilities with AES-256-GCM and tooling for event migration and performance benchmarking.
6 changes
Survey your own repository
Tochemey/ego 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 4db93d7c54 — 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.