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.
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.
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.Application which makes you able to create distributed, high performance and reliable microservice solutions having native integration with Erlang infrastructure.
- 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
gen.Stagebehavior support (originated from Elixir’s GenStage). This is abstraction built on top of
gen.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 run
go run ./examples/genstageto see it in action
gen.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 -
Process.Sendin fashion of
- 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.TermProplistIntoStructor to the string using
- Custom marshaling/unmarshaling via
- Encryption (TLS 1.3) support (including autogenerating self-signed certificates)
- Tested and confirmed support Windows, Darwin (MacOS), Linux, FreeBSD.