Topology as a dedicated layer

Distributed system topology as a dedicated, declared and executable layer.

In most distributed systems, how components communicate — which transport, which serializer, whether two services share a process or run apart — is implicit: encoded in HTTP clients, retry logic, and config scattered across every service that touches it. Itara makes it a single, declared, validated layer instead. Components declare what they do; the wiring configuration declares how they connect; an agent resolves every connection once, before your application runs.

Contributions welcome!

Issues, pull requests, and questions are all welcome on GitHub. A few issues are tagged good-first-issue if you’re looking for somewhere to start.

Read more