Top AI Repos — open-source AI, indexed and scored
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
An actor-based Framework with network transparency for creating event-driven architecture in Golang. Inspired by Erlang. Zero dependencies.
| Date | Stars |
|---|---|
| 2026-07-24 | 4618 |
| 2026-07-25 | 4618 |
| 2026-07-28 | 4621 |
| 2026-07-30 | 4621 |
| 2026-08-06 | 4621 |
Today
— stars today
This week
— stars this week
This month
— stars this month
Momentum
0.0
growth rate 0.00%/day
<h1><a href="https://ergo.services"><img src=".github/images/logo.svg" alt="Ergo Framework" width="159" height="49"></a></h1> [](https://docs.ergo.services) [](https://pkg.go.dev/ergo.services/ergo) [](https://opensource.org/licenses/MIT) [](https://t.me/ergo_services) [](https://reddit.com/r/ergo_services) The Ergo Framework is an implementation of ideas, technologies, and design patterns from the Erlang world in the Go programming language. It is based on the actor model, network transparency, and a set of ready-to-use components for development. This significantly simplifies the creation of complex and distributed solutions while maintaining a high level of reliability and performance. ### Features ### 1. **Actor Model**: isolated processes communicate through message passing, handling messages sequentially in their own mailbox with four priority queues. Processes support both asynchronous messaging and synchronous request-response patterns, enabling flexible communication while maintaining the actor model guarantees. 2. **Network Transparency**: actors interact the same way whether local or remote. The framework uses custom serialization and protocol for [efficient](https://github.com/ergo-services/benchmarks) distributed communication with connection pooling, compression, and type caching, making network location transparent to application code. 3. **Supervision Trees**: hierarchical fault recovery where supervisors monitor child processes and apply restart strategies when failures occur. Supports multiple supervision types (One For One, All For One, Rest For One, Simple One For One) and restart strategies (Transient, Temporary, Permanent) for building self-healing systems. 4. **Meta Processes**: bridge blocking I/O with the actor model through dedicated meta processes that handle TCP, UDP, Port, and Web protocols. Meta processes run blocking operations without affecting regular actor message processing. 5. **Distributed Systems**: service discovery through embedded or external registrars (etcd, Saturn), distributed publish/subscribe events with token-based authorization and buffering, remote process spawning with factory-based permissions, and remote application orchestration across nodes. 6. **Ready-to-use Components**: core framework includes Actor, Supervisor, Pool, and WebWorker actors plus TCP, UDP, Port, and Web meta processes. Extra library provides Leader, Metrics actors, WebSocket, SSE meta processes, Observer application, Colored and Rotate loggers, Erlang protocol support. 7. **Flexibility**: customize network stack components, certificate management, compression and message priorities, logging, distributed events, and meta processes. Framework supports mTLS, NAT traversal, important delivery for guaranteed messaging, and Cron-based scheduling. Examples demonstrating the framework's capabilities are available in the [examples repository](https://github.com/ergo-services/examples). ### Benchmarks ### On a 64-core processor, Ergo Framework demonstrates a performance of **over 21 million messages per second locally** and **nearly 5 million messages per second over the network**.  Available benchmarks can be found in the [benchmarks repository](https://github.com/ergo-services/benchmarks). * Messaging performance (local, network) * Memory consumption per process (demonstrates framework memory footprint) * Seria
Excerpt of 15,864 characters
Read on GitHub
Taras Halturin · @ergo-services
138
Max Treskin · Metachord
50
4
3
Rinor Hoxha · BAITS sh.p.k
2
1
1
vpromzelev · @talon-one
1
Mark deVilliers · United Kingdom
1
1
1
Alexander Petrovsky
1
Dmitri Vereshchagin · Russia
1
1
Would you bet a product on this? Bounded 0–100 and slow moving.
matched fp:76eb197d7f4b7e37, topic:workflow