Skip to main content
GoAkt has been in development since 2022 and runs in production today. This page lists known adopters and the parts of the framework worth configuring before your own launch.

In production

  • Baki Money: AI-powered expense tracking platform that turns receipts into stories.
  • Event Processor: clustered Complex Event Processor (CEP) for IoT data streams.
Running GoAkt in production? Open a discussion or a pull request against the README to be added to this list.

Before you go live

Supervision

Decide how each actor subtree fails: directives, restart budgets, and backoff. The defaults are sensible, but payment flows and ingest pipelines rarely want the same policy.

Coordinated shutdown

Register shutdown hooks so deploys and scale-downs drain mailboxes and release resources instead of dropping in-flight work.

Observability

Export system and actor metrics through OpenTelemetry, watch the event stream for lifecycle signals, and monitor dead letters. A rising dead-letter count is usually the first symptom of a bug.

Passivation

Tune idle and capacity-based passivation so memory tracks the working set rather than the total number of entities ever seen.

Service discovery

Pick the provider that matches your platform: Kubernetes, Consul, etcd, NATS, mDNS, DNS-SD, a static list, or the self-managed LAN mode.

Transport security

Enable TLS on remoting; the same configuration also secures cluster transports when clustering is on.

Keeping your deployment secure

Routinely upgrade your Go version and refresh dependencies. GoAkt keeps its own dependencies current and runs vulnerability checks, but the application build is yours. To report a vulnerability, use GitHub’s Report a Vulnerability form.

Getting help

Community support happens in Discussions and on Slack. For priority support on complex topics or to fund new features, consider sponsorship.