spawn
ergo
| spawn | ergo | |
|---|---|---|
| 2 | 32 | |
| 255 | 2,675 | |
| 6.3% | 1.0% | |
| 9.6 | 0.0 | |
| 7 days ago | 2 days ago | |
| Elixir | Go | |
| Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
spawn
- Spawn: A New Approach to Actors
-
Anything close beam/otp for other languages?
https://github.com/eigr/spawn runs on the BEAM but extends distributed actors to other languages.
ergo
-
Actor framework versus standard channels
Ergo Framework does - https://github.com/ergo-services/ergo
-
Anything close beam/otp for other languages?
https://github.com/ergo-services/ergo for golang
- Ergo Framework v.2.2.2 is just released with the new cool feature gen.Pool
-
What are the recommended connection pool libraries written in Golang？
I think you should clarify what exactly you need. If you need something like TCP/UDP socket acceptor pool you may want to try Ergo Framework with ready to use design patterns https://github.com/ergo-services/ergo . Example for TCP https://github.com/ergo-services/examples/tree/master/gentcp, for UDP https://github.com/ergo-services/examples/tree/master/genudp
-
Erlang's not about lightweight processes and message passing
In case if you want to feel a flavour of Erlang in Golang - https://github.com/ergo-services/ergo
-
Is there an equivalent to Elixir / GenServer in Go? Trying to create the same request / response pattern with better performance but not sure where to start.
Besides, something like this already exists, I don’t see the point, but hey to each there own… https://github.com/ergo-services/ergo
-
go-actor: Tiny library for writing concurrent programs in Go using actor model
Thanks for sharing. Looks good as a first attempt in the long way to production state. You may also want to take a look another approach of actor based implementation https://github.com/ergo-services/ergo
-
Anyone built an app using Ergo framework?
It looked very different than all the other frameworks I have seen. https://github.com/ergo-services/ergo/blob/master/examples/http/app.go
-
Can Go have let it crash goroutine like in Erlang?
If you love the Erlang way you may want to try ergo framework https://github.com/ergo-services/ergo
What are some alternatives?
jockey - 🏇 Generic Python library for running asynchronous workers. Useful for building event handlers, web frameworks, and alike.
micro - A Go service development platform
spotless - Serverless Gleam
wesher - wireguard overlay mesh network manager
exos - Exos is a simple Port Wrapper : a GenServer which forwards cast and call to a linked Port.
ristretto - A high performance memory-bound Go cache
Akka - Build highly concurrent, distributed, and resilient message-driven applications on the JVM
yggdrasil-go - An experiment in scalable routing as an encrypted IPv6 overlay network
Vert.x - Vert.x is a tool-kit for building reactive applications on the JVM
Pyrlang - Erlang node implemented in Python 3.5+ (Asyncio-based)
dapr - Dapr is a portable, event-driven, runtime for building distributed applications across cloud and edge.
exo - A process manager & log viewer for dev