heathen
Quite interesting article Google brought me. Didn’t find any mentions about it here.
What do you think in general? Would you use together with Elixir or even migrate to more performant language if it would offer similar to OTP features and reliability?
P.S. I don’t have any connection to this project or its authors, I saw it in yesterday’s article selection in Google app on my phone.
Ergo
Technologies and design patterns of Erlang/OTP have been proven over the years. Now in Golang. Up to x5 times faster than original Erlang/OTP in terms of network messaging. The easiest way to create an OTP-designed application in Golang.
Purpose
The goal of this project is to leverage Erlang/OTP experience with Golang performance. Ergo Framework implements DIST protocol, ETF data format and OTP design patterns gen.Server, gen.Supervisor, gen.Application which makes you able to create distributed, high performance and reliable microservice solutions having native integration with Erlang infrastructure.
Features
- Support Erlang 24 (including Alias and Remote Spawn features)
- Spawn Erlang-like processes
- Register/unregister processes with simple atom
gen.Serverbehavior support (with atomic state)gen.Supervisorbehavior support with all known restart strategies support- One For One
- One For All
- Rest For One
- Simple One For One
gen.Applicationbehavior support with all known starting types support- Permanent
- Temporary
- Transient
gen.Stagebehavior support (originated from Elixir’s GenStage). This is abstraction built on top ofgen.Serverto provide a simple way to create a distributed Producer/Consumer architecture, while automatically managing the concept of backpressure. This implementation is fully compatible with Elixir’s GenStage. Example is here examples/genstage or just rungo run ./examples/genstageto see it in actiongen.Sagabehavior support. It implements Saga design pattern - a sequence of transactions that updates each service state and publishes the result (or cancels the transaction or triggers the next transaction step).gen.Sagaalso provides a feature of interim results (can be used as transaction progress or as a part of pipeline processing), time deadline (to limit transaction lifespan), two-phase commit (to make distributed transaction atomic). Here is example examples/gensaga.- Connect to (accept connection from) any Erlang node within a cluster
- Making sync request
ServerProcess.Call, async -ServerProcess.CastorProcess.Sendin fashion ofgen_server:call,gen_server:cast,erlang:sendaccordingly - Monitor processes/nodes
- local → local
- local → remote
- remote → local
- Link processes
- local ↔ local
- local ↔ remote
- remote ↔ local
- RPC callbacks support
- embedded EPMD (in order to get rid of erlang’ dependencies)
- Experimental observer support
- Unmarshalling terms into the struct using
etf.TermIntoStruct,etf.TermProplistIntoStructor to the string usingetf.TermToString - Custom marshaling/unmarshaling via
MarshalandUnmarshalinterfaces - Encryption (TLS 1.3) support (including autogenerating self-signed certificates)
- Tested and confirmed support Windows, Darwin (MacOS), Linux, FreeBSD.
2025 Update:
Where Next?
Trending in Discussions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Courses that'll move you from confusion to "Aha, now I get it!"
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #ai
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 10- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
marcin
Amazing that OTP paradigm is winning new hearts and minds!
I think it also depends on the taste in programming language - which one lets you express your idea with more ease.
Elixir is also a functional language with features and design like patter matching, tail recursion and focus on simple data types (lists/tuples/maps). I personally would be missing these features if I switched to Golang.
Do I understand that ergo provides some sort of binary compatibility so you could have a cluster of elixir and golang nodes? That’s very cool.
heathen
Yes, from what I understood it does, I’m also quite excited about it.
From my own perspective I don’t think this project is able totally replace Beam VM, at least before golang gets immutability and total process (goroutines) isolation (it doesn’t do both, right? not quite sure about the last part, but it shouldn’t). But it would help to add “computation” nodes which can handle heavy calculations and the main part would do the rest.
LostKobrakai
Clustering is based on TCP and the erlang term format. OTP has support for C backed nodes in erlang clusters: Erl_Interface User's Guide — OTP 29.0.2 (erl_interface 5.8.1)
halturin
Thanks for the mention my project here
I’ve released the next version of Ergo Framework 2.1.0 with cool features (compression, proxy, etc..) . Full changelog is here GitHub - ergo-services/ergo: An actor-based Framework with network transparency for creating event-driven architecture in Golang. Inspired by Erlang. Zero dependencies. · GitHub
Happy coding
crispinb
In a similar spirit of imitation being the sincerest form of flattery, I came across GitHub - lunatic-solutions/lunatic: Lunatic is an Erlang-inspired runtime for WebAssembly · GitHub the other day. Both look interesting (and impressively ambitious). Joe Armstrong et al were clearly on to something.
halturin
I’m proudly announce the next release - Ergo Framework 2.2 with key features:
Full changelog: GitHub - ergo-services/ergo: An actor-based Framework with network transparency for creating event-driven architecture in Golang. Inspired by Erlang. Zero dependencies. · GitHub
domehead100
Ergo looks really neat. Some questions/thoughts…
Are there any plans for documentation or guides?
https://docs.ergo.services/ is basically the GitHub readme and then nothing but a skeleton of topic headings with no content.
Is the assumption that someone hoping to use this would be expert enough in both Elixir and Golang to just translate Elixir and OTP docs into Ergo?
The name “Ergo”, while being both catchy and semantically accurate, is unfortunately eclipsed in Google searches by the Ergo platform for blockchain.
Does Ergo implement (or inherit from Go) any kind of work-stealing scheduling or reductions like the Beam or lunatic, or do functions run to completion without interruption?
dimitarvp
I’ve been meaning to try Ergo for months and things are finally starting to come to the point where I’ll have the time – and I have the perfect project for it.
Expect some feedback in the future!
halturin
In case you wondered how it is going …
Ergo Framework 3.0 has been released. A bunch of new stuff there… see changelog GitHub - ergo-services/ergo: An actor-based Framework with network transparency for creating event-driven architecture in Golang. Inspired by Erlang. Zero dependencies. · GitHub
halturin
I’m excited to announce Ergo Framework v3.1.0, bringing significant enhancements to Go’s actor model implementation with great news for the Erlang/Elixir community.
Major Highlight for Erlang/Elixir Developers
Erlang Network Stack License Change: The Erlang protocol implementation has been moved back from BSL 1.1 to MIT license, making it freely available for all commercial and open-source projects. This means seamless interoperability between your Go services built with Ergo and existing Erlang/Elixir systems without licensing concerns.
Key Features in this release
Core Enhancements:
External Library Ecosystem:
Performance
Over 21M messages/sec locally and 5M messages/sec over network on 64-core systems. EDF serialization performs competitively with Protobuf across most data types.
Resources
For detailed changelog see the README.md at GitHub - ergo-services/ergo: An actor-based Framework with network transparency for creating event-driven architecture in Golang. Inspired by Erlang. Zero dependencies. · GitHub This makes it easier than ever to build hybrid systems combining the best of Go’s performance with Erlang/Elixir’s proven concurrency model!