https://github.com/ergo-services/examples
examples for demonstrating Ergo Framework features
https://github.com/ergo-services/examples
Last synced: about 2 months ago
JSON representation
examples for demonstrating Ergo Framework features
- Host: GitHub
- URL: https://github.com/ergo-services/examples
- Owner: ergo-services
- License: mit
- Created: 2023-01-27T15:20:59.000Z (over 2 years ago)
- Default Branch: master
- Last Pushed: 2025-03-04T13:53:04.000Z (3 months ago)
- Last Synced: 2025-04-01T12:03:59.953Z (2 months ago)
- Language: Go
- Size: 143 KB
- Stars: 35
- Watchers: 2
- Forks: 4
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
[](https://docs.ergo.services)
[](https://t.me/ergo_services)
[](https://x.com/ergo_services)
[](https://reddit.com/r/ergo_services)
[](https://discord.gg/xHEa7KzX)Here you can find examples demonstrating features of Ergo Framework 3.0 (and above).
## demo
This is an "umbrella"-example that demonstrates most of the Ergo Framework features. It was generated by `ergo` tool with just a single command. See `README.md` file in [demo](demo) for the details.

## call
This example project shows how to make synchronous requests to the local and remote processes. It starts two nodes (`node1@localhost` and `node2@localhost`); `node1` spawns processes `a` and `b`; `node2` spawns process `b`. Process `a` is making `Call` requests sequentially to the process `b` on `node1@localhost` (locally) and to the process `b` on `node2@localhost` (remotely)

## events
Ergo Framework provides the "Events" feature that implements the distributed "Publisher/Subscriber" design pattern. This example demonstrates this feature in action. It starts node `node-pub@localhost` with a producer process and second node `node-sub@localhost` with two consumer processes.
## erlang
This example demonstrates how the node built with Ergo Framework and enabled Erlang network stack natively communicates with the Erlang node.

## websocket
The following example starts Web server with websocket-handler at "/" and spawns 3 processes to handle websocket-connections.