Ergo: Erlang-inspired event driven actor framework in Go

• ergo

  35 3,610 3.5 Go

  An actor-based Framework with network transparency for creating event-driven architecture in Golang. Inspired by Erlang. Zero dependencies.

  

• SaaSHub

  www.saashub.com featured

  SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

  

• examples

  3 30 3.5 Go

  examples for demonstrating Ergo Framework features (by ergo-services)

  

  The examples are in another repo:

  https://github.com/ergo-services/examples

• laborunion

  1 27 - Go

  Dynamic Worker Pool Library

  I have been watching Ergo repo for a while now and you wrote my observation concisely.

  A while back, I tried to solve no.2 on your list by having a dynamically expanding and shrinking go-routines. POC here: https://github.com/didip/laborunion. It is meant to be used in-conjunction with config library & application object that's update-able over the wire. But I never got around to solve that last part.

• redwood

  2 869 0.0 Go

  A highly-configurable, distributed, realtime database that manages a state tree shared among many peers. (by brynbellomy)

  

  with that said it’s quite easy to write an equivalent- https://github.com/redwood/redwood/blob/develop/utils/mailbo...

• Akka.net

  21 4,701 9.4 C#

  Canonical actor model implementation for .NET with local + distributed actors in C# and F#.

  

  No per-process GC (still very configurable unlike the one here) but for hot-reload, if you don't mind completely different language, there are https://github.com/akkadotnet/akka.net and https://github.com/dotnet/orleans

• Orleans

  36 10,067 9.1 C#

  Cloud Native application framework for .NET

  

  No per-process GC (still very configurable unlike the one here) but for hot-reload, if you don't mind completely different language, there are https://github.com/akkadotnet/akka.net and https://github.com/dotnet/orleans

• protoactor-go

  19 5,055 8.6 Go

  Proto Actor - Ultra fast distributed actors for Go, C# and Java/Kotlin

  

  My go to actor framework for golang has always been https://github.com/asynkron/protoactor-go. It seems that both protoactor and ergo are heavily influenced by Erlang. Why would one select ergo over protoactor?

• Oragono

  23 2,265 8.3 Go

  A modern IRC server (daemon/ircd) written in Go.

  

  Not to be confused with ergo, the ircd[0] nor with ergo, the cryptocurrency[1]

  [0] https://github.com/ergochat/ergo

  [1] https://github.com/ergoplatform

• .NET Runtime

  654 15,087 10.0 C#

  .NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.

  

• asyncmachine-go

  2 70 9.2 Go

  non-blocking state machine for workflows

  > you cannot send messages directly to a goroutine

  Goroutines communicate through channels, all you need is a queue (eg buffered chan).

  > you cannot terminate a goroutine from another goroutine

  Termination is propagated via context cancellation. go-A cancels ctx, go-B waits with `select`, reads from `<-ctx.Done()` and does a `return`, or checks it after each blocking call.

  > there are no "goroutine-local variables"

  Not sure if I got this one, but every var in a function's scope, which has been `go`-routined, would qualify.

  I'm currently working on a lib/framework somehow related to Ergo, but taking a more "generic" approach of a state machine[0]. It may solve some of the mentioned issues with Go, like addressing and queues for communication.

  You seem to be very attached to an idea of using the same goroutine for a long time, whereas it's usually more dynamic and only schedulers are long lived `go`-s.

  [0]: https://github.com/pancsta/asyncmachine-go

Suggest a related project