Here you can find examples demonstrating features of Ergo Framework 3.0 (and above).
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 for the details.
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)
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.
This example demonstrates how the node built with Ergo Framework and enabled Erlang network stack natively communicates with the Erlang node.
The following example starts Web server with websocket-handler at "/" and spawns 3 processes to handle websocket-connections.
Demonstrates running a multi-node Ergo cluster in Docker with etcd as a registrar. Three nodes discover each other through etcd, exchange messages, and react to real-time configuration changes. Shows service discovery, actor communication across nodes, typed hierarchical configuration, and cluster event monitoring.
The Ergo Framework allows you to run external programs and interact with them using standard input and output. This example demonstrates this functionality. It launches two programs: one that uses a text format for communication, and another that uses a binary format.
Demonstrates Ergo Framework's built-in observability stack: a 5-node cluster running realistic workloads with Prometheus metrics collection, pre-configured Grafana dashboards, Observer web UI, and MCP-based cluster diagnostics via Claude Code. Includes four scenario applications (latency, messaging, lifecycle, events) that generate different types of load to exercise all framework metrics. Runs with Docker Compose.
Demonstrates the Radar application -- a sidecar that bundles Kubernetes health probes and Prometheus metrics on a single HTTP port. Three demo workers (database, cache, API gateway) register health signals and update custom metrics through Radar helper functions.