Skip to main content
GoAkt home page
GoAkt
Search...
βK
Reference
GitHub
Search...
Navigation
Clustering
Standalone Mode
Getting Started
π Introduction
π¦ Installation
π Migration from v3.x
Actor
π First Actor
π Actor Model
βοΈ Actor System
π PID
π¬ Messaging
π Actor Lifecycle
π‘οΈ Supervision
π Location Transparency
π¬ Behaviors
π₯ Stashing
ποΈ Death Watch
β‘οΈ PipeTo
π Reentrancy
π€ Passivation
π Relocation
π Cluster Singletons
π Routers
β° Scheduling
π§ͺ TestKit
Grains
πΎ Grains
Advanced
π‘ Remoting
π Client
π¦ Serialization
π§ Extensions and Dependencies
π» Event Streams
π’ PubSub
π Observability
π Distributed Data
π Streams
π Coordinated Shutdown
Clustering
π₯οΈ Standalone Mode
π Clustered Mode
π Multi-Datacenter
π Service Discovery
Architecture
ποΈ Architecture Overview
πΊοΈ Code Map
π Design Decisions
Contributing
π€ Contributing Overview
π οΈ Development Setup
β Testing Strategy
π Extending GoAkt
Reference
π Interfaces Reference
π API Changes (v4.0.0)
π Glossary
Meta Framework
π§ eGo
On this page
Overview
When to use
Configuration
Limitations
Clustering
Standalone Mode
Single-node actor system without clustering.
β
Overview
In standalone mode, GoAkt runs in a single process. All actors communicate in-process. No network or cluster setup is required.
β
When to use
Development and testing
Single-node deployments
Services that donβt need distribution
β
Configuration
Create an actor system with
NewActorSystem
and
Start
. No remoting or cluster options are needed. Actors are spawned under the user guardian and communicate via direct mailbox enqueue.
β
Limitations
No remoting: actors cannot span multiple processes
No clustering: no discovery, no relocation, no cluster singletons
Single point of failure: process crash stops everything
For multi-node deployments, see
Clustered
.
Coordinated Shutdown
Previous
Clustered Mode
Next
βI